svn commit: r39468 - head/en_US.ISO8859-1/books/handbook/ports

[Benjamin Kaduk]

On Wed, 29 Aug 2012, Isabell Long wrote:

> Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.sgml
> ==============================================================================
> --- head/en_US.ISO8859-1/books/handbook/ports/chapter.sgml	Wed Aug 29 05:59:54 2012	(r39467)
> +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.sgml	Wed Aug 29 14:29:03 2012	(r39468)
> @@ -976,6 +976,18 @@ docbook                     =
> 	    <command>make <maketarget>install</maketarget></command> and
> 	    <command>make <maketarget>clean</maketarget></command>
> 	    as three separate steps.</para>
> +
> +	  <para>When installing a port, using only <command>make
> +	      <maketarget>install</maketarget></command> from the
> +	    beginning means there will potentially be many waiting
> +	    periods between user interaction as the default behaviour
> +	    is to prompt the user for options.  When there are many
> +	    dependencies, this sometimes makes building a single port
> +	    a huge hassle.  To avoid this, first run <command>make
> +	      <maketarget>config-recursive</maketarget></command> to
> +	    do the configuration in one batch.  Then run

Is this actually true these days?  I seem to recall that (at least 
pre-optionsng), if you changed port options so as to add new dependencies, 
the new dependencies were not included in the config-recursive step, 
requiring that 'make config-recursive' was run in a loop until it had 
nothing more to configure.

-Ben Kaduk

> +	    <command>make <maketarget>install
> +	      [clean]</maketarget></command> afterwards.</para>