Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Mar 2002 14:35:52 -0600
From:      Sean O'Neill <sean@seanoneill.info>
To:        Roman Neuhauser <neuhauser@mobil.cz>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: mod_php4_standalone port - someone want to help me clean this thing up?
Message-ID:  <5.1.0.14.0.20020327142146.00ae9da0@postoffice.swbell.net>
In-Reply-To: <20020327202631.GS389@roman.mobil.cz>
References:  <5.1.0.14.0.20020327134816.00ac94d0@postoffice.swbell.net> <5.1.0.14.0.20020327134816.00ac94d0@postoffice.swbell.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At 09:26 PM 3/27/2002 +0100, Roman Neuhauser wrote:
>     Hi Sean, I thought I stated this in my previous reply: such port
>     already exists in /usr/ports/lang/php4. All it does is compile
>     /usr/ports/www/mod_php4 with STANDALONE=yes.
>     Looks like you wasted your time. (Or am I missing something?)

Just to make sure I wasn't missing something - I deinstalled my mod_php4 
and recompiled it with STANDALONE=yes.  This is what happened:

1) /usr/local/bin/php got installed and I think that's it.
2) The pkglist that got put into the pkg DB is the package list for 
everything EXCEPT /usr/local/bin/php.  So the pkg DB is now whacked in 
respect to mod_php4.  There are files for pkg-comment and pkg-plist with 
".standalone" extensions but the make/installation process doesn't appear 
to use them.  It is apparent that the pkg-comment.standalone and 
pkg-plist.standalone files need to be manually moved in place of their 
respective counter-parts.

I went down this new port path because of the following in a previous post 
of yours on this topic:

 > as for the double install problem: you can add -DFORCE_PKG_REGISTER
 > to the make command line, but that'll make it hard for you to remove
 > the previous install files later: the plist will get overwritten,
 > listing e. g. /usr/local/bin/php instead of
 > /usr/local/lib/mod_php4.so (or wherever it is).
 >
 > what I'd recommend is copy the port skeleton, and hack the makefile
 > to create another port (which should be done anyway)...

So with your suggestion, and because I didn't want to have the "double 
install problem", I created the new port.  With the new port, the package 
list for both package is correct in respect to what they installed and 
don't appear to cause a "double install problem."


--
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20020327142146.00ae9da0>