Date: Tue, 31 Aug 2004 21:42:30 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Thierry Thomas <thierry@FreeBSD.org> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/sysutils/pear-Log Makefile Message-ID: <E59045D3-FB85-11D8-B720-00039312D914@fillmore-labs.com> In-Reply-To: <20040831184212.GA52389@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thierry Thomas wrote: > Le Mar 31 aoû 04 à 19:46:10 +0200, Oliver Eikemeier > <eikemeier@fillmore-labs.com> > écrivait : >> This hardcodes LOCALBASE as /usr/local, besides ports should avoid >> variables beginning with an underscore, since they are often used as >> bsd.port.mk private variables. > > Yes, pear-PEAR/Makefile.common uses such variables. Of course, they > could be renamed, if needed, but that would imply modifications in a lot > of pear-* ports. Perhaps we can integrate this either in bsd.php.mk or make an bsd.pear.mk out of it. Variables starting with an underscore shouldn't be used in ports, and there should be no global configuration file in /usr/local/etc. Besides, this might gives us the chance to make this PREFIX safe. >> Besides, looking at pear-PEAR/Makefile.common is looks like pear ports >> are inherently not PREFIX safe, or am I wrong here? > > Pear ports cannot be strictly PREFIX safe: they are PHP_BASE safe. > There is the same problem with some ports which need to install under > X11BASE, or Apache modules, or mozilla extensions, etc. There is no such thing as a PHP_BASE. Ports have to install all their files into PREFIX. X11BASE is settable in bsd.port.mk, we are working on the problem of the apache modules, and mozilla extensions are PREFIX safe AFAIK. Besides, it looks like specifying a different PREFIX/LOCALBASE will break the packing list. -Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E59045D3-FB85-11D8-B720-00039312D914>