From owner-cvs-all@FreeBSD.ORG Tue Aug 31 19:42:13 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88E5516A4CE; Tue, 31 Aug 2004 19:42:13 +0000 (GMT) Received: from fillmore.dyndns.org (port-212-202-49-192.dynamic.qsc.de [212.202.49.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D10B43D48; Tue, 31 Aug 2004 19:42:13 +0000 (GMT) (envelope-from eikemeier@fillmore-labs.com) Received: from dhcp-10.local ([172.16.0.10] helo=dhcp-11.local) by fillmore.dyndns.org with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.42 (FreeBSD)) id 1C2EWA-000D0Y-3M; Tue, 31 Aug 2004 21:42:12 +0200 Date: Tue, 31 Aug 2004 21:42:30 +0200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v482) To: Thierry Thomas From: Oliver Eikemeier In-Reply-To: <20040831184212.GA52389@graf.pompo.net> Message-Id: Content-Transfer-Encoding: quoted-printable User-Agent: KMail/1.5.9 cc: =?ISO-8859-1?Q?Ant=F4nio_Carlos_Ven=E2ncio_J=FAnior?= cc: cvs-ports@FreeBSD.org cc: Pav Lucistnik cc: cvs-all@FreeBSD.org cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/sysutils/pear-Log Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 19:42:13 -0000 Thierry Thomas wrote: > Le Mar 31 ao=FB 04 =E0 19:46:10 +0200, Oliver Eikemeier=20 > > =E9crivait=A0: >> 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=20 bsd.pear.mk out of it. Variables starting with an underscore shouldn't=20= be used in ports, and there should be no global configuration file in=20 /usr/local/etc. Besides, this might gives us the chance to make this=20 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=20 files into PREFIX. X11BASE is settable in bsd.port.mk, we are working on=20= the problem of the apache modules, and mozilla extensions are PREFIX=20 safe AFAIK. Besides, it looks like specifying a different PREFIX/LOCALBASE will=20 break the packing list. -Oliver