make config-recursive

Guillermo MORENO-SOCIAS Guillermo.Moreno-Socias at math.uvsq.fr
Mon Feb 27 10:54:33 PST 2006


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


More information about the freebsd-ports mailing list