configure recursively and build question

[Lowell Gilbert]

Istvan Gabor <suseuser04 at lajt.hu> writes:

> 2013. március 12. 21:17 napon Lowell Gilbert <freebsd-questions-local at be-well.ilk.org> írta:
>> 
>> Second, config-recursive only does the configuration of the port
>> options.
>
> Then I misunderstood the handbook, chich says:
>
> "To avoid this when there are many dependencies, first run make config-recursive
> to do the configuration in one batch."
>
> I understood this as the configuration is done on all the dependencies as well.

You understood the handbook correctly. My comment was poorly worded and
unnecessary (I was actually making the same point as in #4.

The word "options" can mean slightly different things. The port's
framework may define options, which the port will require you to choose
among before building its software. The program being built may
*additionally* require user input for building, and the port framework
(in particular, "make config") can't store those choices. This is
unusual, but some common ports do it (for example, ghostscript is one).

> The handbook also writes:
>
> "Tip: When using config-recursive, the list of ports to configure are gathered by the
> all-depends-list make(1) target. It is often recommended to run make config-recursive
> until all dependent ports options have been defined, and ports options dialog(1) screens
> no longer appear, to be certain all ports options have been configured as intended."
>
> Does this mean if I run config-recursive several times in a raw, all the dependencies will
> be configured?

This is a slightly different issue. Changing a port's options may change
its dependencies, so another round of config-recursive  might be needed
to config the new dependencies.

> ...
>
>> Fourth (and, you'll be glad to hear, finally) some ports are interactive
>> for reasons beyond options. See the manual for ports(7), noting the
>> environment variables INTERACTIVE and BATCH.
>
> I will look at this.
>
>> > Second, after I've done a configure-recursive, how can I start it over from scratch in case
>> > I want to change some config option? If I reissue make configure-recursive,
>> > I get only no configuration needed messages.
>> 
>> If you really want to start from scratch, you can use
>> "rmconfig-recursive" on the dependent port.
>
> Yes I meant only the given port and its dependencies, not the all ports.