Date: Tue, 31 Aug 2004 20:42:12 +0200 From: Thierry Thomas <thierry@FreeBSD.org> To: Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/sysutils/pear-Log Makefile Message-ID: <20040831184212.GA52389@graf.pompo.net> In-Reply-To: <A5354FFC-FB75-11D8-B720-00039312D914@fillmore-labs.com> References: <200408311457.i7VEvXDO064188@repoman.freebsd.org> <A5354FFC-FB75-11D8-B720-00039312D914@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le Mar 31 ao=FB 04 =E0 19:46:10 +0200, Oliver Eikemeier <eikemeier@fillmore= -labs.com> =E9crivait=A0: > This hardcodes LOCALBASE as /usr/local, besides ports should avoid=20 > variables beginning with an underscore, since they are often used as=20 > 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. > Besides, looking at pear-PEAR/Makefile.common is looks like pear ports=20 > 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. Regards, --=20 Th. Thomas. --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBNMaDc95pjMcUBaIRAg8JAJ9VmPFFk/WC/PMvjLDDu2MkhGu47ACg+Adc Ch+IBxvyf9sn+CeNv6oXx1E= =GVtc -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040831184212.GA52389>