Date: Sat, 28 Jul 2007 22:37:50 +0100 From: "N.J. Mann" <njm@njm.f2s.com> To: CyberLeo Kitsana <cyberleo@cyberleo.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Custom builds from ports Message-ID: <20070728213750.GA93017@oberon.njm.f2s.com> In-Reply-To: <46AB9EB4.5080305@cyberleo.net> References: <46AB9EB4.5080305@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <46AB9EB4.5080305@cyberleo.net>, CyberLeo Kitsana wrote:
>
> My question concerns building ports with custom options.
>
> With some ports, 'make config' governs the options, and stores them in a
> file someplace so they are honored the next time you build or upgrade
> the port.
>
> With most ports, however, this is controlled by passing variables on the
> command line or via the environment.
>
> The most obvious location for these variables to be placed, so that they
> may affect recursive builds and upgrades, is make.conf. However, I've
> noticed that some ports use the same variable names for similar options
> ('WITH_MYSQL'), when I may not want that option set in both ports.
>
> Is there a way to specify which ports certain options are to be applied
> to, without having to craft custom command lines and build ports
> individually?
Is ports-mgmt/portconf what you are looking for?
Cheers,
Nick.
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070728213750.GA93017>