Date: Sun, 21 Jan 2007 00:19:24 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Modifying a port and keeping the mods across updates Message-ID: <20070121001924.1528c7b9@gumby.homeunix.com> In-Reply-To: <p06240848c1d82f42c0e3@[10.20.30.108]> References: <p06240841c1d75354626b@10.20.30.108> <790a9fff0701192137y703108i421c05422eda39a7@mail.gmail.com> <p06240844c1d80886acef@10.20.30.108> <790a9fff0701201048scc83967s4edf1dae74437d39@mail.gmail.com> <p06240848c1d82f42c0e3@[10.20.30.108]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Jan 2007 12:44:59 -0800
Paul Hoffman <phoffman@proper.com> wrote:
> At 12:48 PM -0600 1/20/07, Scot Hetzel wrote:
> >Are you trying to add NSS_ENABLE_ECC to the MAKE_ENV?
> >
> >Normally you would put it in ports.conf as:
> >
> >security/nss: MAKE_ENV+= NSS_ENABLE_ECC=1
>
> Boy, that wasn't clear in the four lines of info on portconf.
>
portconf is simply a quick way of adding entries to make.conf without
having to put in explicit conditional statements like:
.if ${.CURDIR:M*/x11-toolkits/qt33}
WITH_KDE_PATCHES=yes
.endif
What actually works as an entry depends on the ports system and each
individual port makefile. It's primary use is setting portknobs. With
something like MAKE_ENV+=.. you are depending on the port Makefile
not setting MAKE_ENV or setting it with a "+=" rather than "=".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070121001924.1528c7b9>