You I<may> list options here which are I<conceptually> limited to a single
configuration step. For example, if you wished to skip validation of the
F<MANIFEST> during configuration and to configure without ICU, you I<could>,
in this section, say:
However, as we shall quickly see, it's conceptually clearer to place these
values next to those configuration steps that actually use them.
Section begins with line C<=steps> and must be followed by at least one
blank line, in turn followed by the list of configuration steps, followed by
another blank line followed by a line C<=cut> (just like POD).
The order in which you list the steps is the order in which they will be
executed. If you delete a step from the canonical list or comment a step out,
it will not be executed.
In the above example, step C<auto::perldoc> will be completely skipped. You
will not see it listed as C<....skipped> in F<Configure.pl>'s output; it will
simply not be there at all.
This is the recommended location to call options whose impact is
I<conceptually> limited to a single configuration step. Type the
configuration step's name, type a whitespace, type the option (with no leading
C<-->) and repeat as needed for additional step-specific options.
This is also the location to call options whose impact is limited to one step
at a time but which may be applied to more than one configuration step. The
C<fatal-step> and C<verbose-step> options are the best examples of this case.
Rather than requesting verbose output from all configuration steps, you may,
for example, wish to designate only a few steps for verbose output: