Date: Mon, 23 Feb 2004 13:27:16 -0800 From: Kris Kennaway <kris@obsecurity.org> To: freebsd-ports@freebsd.org, portmgr@freebsd.org Subject: Re: Global ports customization Message-ID: <20040223212716.GA29804@xor.obsecurity.org> In-Reply-To: <20040223211817.GA53330@mossy.its.rndex.ru> References: <20040223211817.GA53330@mossy.its.rndex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--sm4nu43k4a2Rpi4c
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 24, 2004 at 12:18:17AM +0300, Rodion Novoselov wrote:
> Hello.
>=20
> I'm used to putting down customization things for ports into
> /etc/make.conf file. However, I consider it to be a pretty wrong place
> because /etc/make.conf is included implicitly every time make runs no
> matter whether I build a port or something else. Having looked
> bsd.port.mk through I've found an opportunity to add a per-port
> customization via ${PORTSDIR}/${PORTORIGIN}/Makefile.local. Why
> shouldn't do the same stuff for the ports collection at whole and add
> something like:
>=20
> .if exists(${PORTSDIR}/Makefile.local)
> .include "${PORTSDIR}/Makefile.local"
> .endif
>=20
> to bsd.port.mk?
Frankly I don't really see the need. The problem of /etc/make.conf
being used for non-port makes is not significant.
Kris
--sm4nu43k4a2Rpi4c
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAOnA0Wry0BWjoQKURArvbAJ41hCS2wKLYkvVG79Zvjf0zJ30q0wCfX4np
pif2g2b4dCCmpxSA18CCmzU=
=vrrE
-----END PGP SIGNATURE-----
--sm4nu43k4a2Rpi4c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040223212716.GA29804>