Which ports store/use OPTIONS (/var/db/ports/portname/options)?
Scot Hetzel
swhetzel at gmail.com
Mon Feb 27 10:49:04 PST 2006
On 2/27/06, Ade Lovett <ade at freebsd.org> wrote:
>
> On Feb 27, 2006, at 09:47 , Scot Hetzel wrote:
> > NOTE: reason 2 & 3 can be solved by setting the BATCH variable when
> > building the port, but it then doesn't allow you to set OPTIONS on the
> > first time the port is built. Instead it uses the ports default
> > options.
>
> That's what "make config-recursive" is for. When installing
> something through ports that is likely to have a bunch of
> dependencies, some of which may have options, and you want to leave
> the build unattended, it becomes a two stage process:
>
Thanks for the tip on config-recursive.
Just one question, does config-recursive also show the options for
optional dependancies?
For example, your building a port (with options) and use 'make
config-recursive'. You enable a option in the port (was previously
unchecked), which causes a dependancy (LIB, RUN, ..) on another port
that also has options. Will config-recursive show a dialog for the
optional dependancy port or will a second 'make config-recursive' be
needed?
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
More information about the freebsd-ports
mailing list