Date: Sat, 21 Aug 2004 08:32:27 +0300 From: "ports@c0decafe.net" <ports@c0decafe.net> To: freebsd-ports@freebsd.org Subject: Re: FreeBSD ports which are currently scheduled for deletion Message-ID: <pan.2004.08.21.05.31.16.379387@c0decafe.net> References: <20040820181220.4405c774.sheepkiller@cultdeadsheep.org> <C29D63C1-F2CE-11D8-A951-00039312D914@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Aug 2004 20:31:24 +0200, Oliver Eikemeier wrote:
> Ok, first you determine APXS_PREFIX. Since apache is installed in
> ${LOCALBASE} (and APXS is therefore ${LOCALBASE}/sbin/apxs), this is
> ${LOCALBASE} too.
>
> Ah, I see. You try to cope with the fact that apxs erroneously installes
> files in LOCALBASE instead of PREFIX:
>
> @cwd ${APXS_PREFIX}
> @unexec %D/sbin/apxs -e -A -n %%AP_NAME%%
> %D/%%APACHEMODDIR%%/%%AP_MODULE%%
> %%APACHEMODDIR%%/%%AP_MODULE%%
> @exec %D/sbin/apxs -e -A -n %%AP_NAME%% %D/%F @cwd ${PREFIX}
>
> The problem with that is that you call ${APXS_PREFIX}/sbin/apxs, which
> doesn't matter here, since LOCALBASE = APXS_PREFIX, but won't work
> otherwise. Besides, packages will ignore every -p given to pkg_add(1).
the trick here, is to not set PREFIX for individual modules, but to reset
APXS to whatever your (custom, else there is no problems, right?) apache
prefix is, and it will do the right thing (tm), at least for some :)
unless i am misunderstanding the problem here?
> So, as far as I understand the situation, it's apxs that should be fixed
> to honor PREFIX, and everything should be fine without the need for the
> hacks in the packing list.
>
> Which means something like:
>
modules need to follow the apache installation, unless there is value in
independent prefixes for them?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?pan.2004.08.21.05.31.16.379387>