Date: Mon, 27 Feb 2006 19:54:25 +0100 From: Guillermo MORENO-SOCIAS <Guillermo.Moreno-Socias@math.uvsq.fr> To: freebsd-ports@freebsd.org Subject: make config-recursive Message-ID: <20060227185425.GA96775@math.uvsq.fr> 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 Mon, Feb 27, 2006 at 10:08:51AM -0800, Ade Lovett 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:
>
> cd /usr/ports/foo/bar
> make config-recursive
> ...
> [it'll trawl through the dependency chain, popping up the OPTIONS
> dialog for any ports]
> ...
> make install
I hope this is not a too naive question. Is it possible to have
this "make config-recursive" thing when doing "portupgrade -aRr"?
Guillermo Moreno-Socias
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060227185425.GA96775>