Date: Mon, 23 Feb 2004 16:30:06 -0500 From: "Walter Venable" <weaseal@hotmail.com> To: kris@obsecurity.org, freebsd-ports@freebsd.org, portmgr@freebsd.org Subject: Re: Global ports customization Message-ID: <LAW10-F45A6Zi6qWqRW0000db38@hotmail.com>
next in thread | raw e-mail | index | archive | help
Regardless, you can always submit your patch via send-pr, if you like.
Walter Venable
>From: Kris Kennaway <kris@obsecurity.org>
>To: freebsd-ports@freebsd.org, portmgr@freebsd.org
>Subject: Re: Global ports customization
>Date: Mon, 23 Feb 2004 13:27:16 -0800
>
>On Tue, Feb 24, 2004 at 12:18:17AM +0300, Rodion Novoselov wrote:
> > Hello.
> >
> > 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:
> >
> > .if exists(${PORTSDIR}/Makefile.local)
> > .include "${PORTSDIR}/Makefile.local"
> > .endif
> >
> > 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
><< attach3 >>
_________________________________________________________________
Take off on a romantic weekend or a family adventure to these great U.S.
locations. http://special.msn.com/local/hotdestinations.armx
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LAW10-F45A6Zi6qWqRW0000db38>