Date: Fri, 19 Oct 2007 15:38:05 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: Updating Ports Message-ID: <20071019153805.3b25be0f@gumby.homeunix.com.> In-Reply-To: <18200.44923.816309.975738@jerusalem.litteratus.org> References: <471773D8.80503@mtmary.edu> <18199.32078.807531.40747@jerusalem.litteratus.org> <471786EC.3040803@mtmary.edu> <18199.57951.791968.841899@jerusalem.litteratus.org> <20071019125806.31a8b424@gumby.homeunix.com.> <18200.44923.816309.975738@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Oct 2007 09:22:03 -0400
Robert Huff <roberthuff@rcn.com> wrote:
> RW writes:
>
> > You don't have to set anything globally in make.conf, you can do it
> > like this:
> >
> > .if ${.CURDIR:M*/net-mgmt/net-snmp}
> > WITH_TKMIB=yes
> > .endif
>
> That looks good.
>
> > and that can be simplified by using portconf, which puts a single
> > line in make.conf and reads in the settings from its own
> > configuration file.
>
> This as well, though I see it as reducing (in practice) to my
> solution.
If you use pkgtools.conf, the settings only get picked-up by portupgrade
and tools that can use the ruby libraries. They won't be picked-up
by portmaster, or on a manual "make install" and by other make targets.
If you are trying to diagnose a build problem, or work out what the
Makefiles are actually doing, it's useful to have them pick-up the
actual portknobs. You can wrap the make.conf definitions inside an
".if defined (SUPPRESS_PORTKNOBS) ... .endif" block to turn them off
and on through the environment.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071019153805.3b25be0f>