Date: Mon, 27 Feb 2006 12:48:59 -0600 From: "Scot Hetzel" <swhetzel@gmail.com> To: "Ade Lovett" <ade@freebsd.org> Cc: ports@freebsd.org Subject: Re: Which ports store/use OPTIONS (/var/db/ports/portname/options)? Message-ID: <790a9fff0602271048k764ecc02r6753e143aaed0c59@mail.gmail.com> In-Reply-To: <431EE15A-9498-4387-8DA5-DB293079AC4A@FreeBSD.org> References: <867j7gd8kw.fsf@PECTOPAH.shenton.org> <790a9fff0602270947y5dd9c98dkd26fc17f641cc3e7@mail.gmail.com> <431EE15A-9498-4387-8DA5-DB293079AC4A@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/27/06, Ade Lovett <ade@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0602271048k764ecc02r6753e143aaed0c59>