Andy Dougherty wrote:

>  You can try it right now with
> 
>          perl -MConfig -e 'print Config::config_sh();' > config.sh
>          sh Configure [whatever options you like]
>  
>  You'll find that it's not a very good idea. 

[deletia]

>  The original poster didn't specify which Configure choices needed to be
>  overridden, but my guess is that if any wants to pursue this further, I
>  think the Policy.sh angle is probably the best direction to pursue.

Wise advice.  In looking at the original post I wonder if by the complaint
about being "unable to re-use a Config.pm" the person might actually be
worried about taking an inventory of post perl build installed modules and
being able to reproduce that with the newly installed perl kit.  It seems
to be that a lot of people overlook the information provided by
perllocal.pod and perl does not ship with a util/inventory.PL ->  inventory
script that can pretty print nice tables of what's installed making use of
ExtUtils::Installed.  They also tend to overlook (or simply cannot use
owing to firewall config issues) the capabilities of CPAN.pm and the CPAN
shell.  Hence this may be a documentation issue of some sort.

I note that along with your note about the inadvisability of re-extracting
a config.sh from Config.pm using the information verbatim from
perllocal.pod verbatim may mean that you'll avoid picking up newer
versions of modules that you may want to upgrade with.

I could be wrong about the nature of the complaint though.

Peter Prymmer