Front page | perl.perl5.porters |
Postings from July 2001
From: Jarkko Hietaniemi
July 31, 2001 14:25
Message ID: 20010731162539.W120@chaos.wustl.edu
> It is not doing it automatically; I asked for it. I guess my point
Well, yes. But I don't want to embed the logic of parsing
perllocal.pod into Configure: that's what I meant by automatic.
> is that there should be a more automated way to populate the new Perl
> with all of the existing site-specific modules. Would you feel more
> inclined if it required
> instead? I am thinking of times when there is not likely to be
> binary compatibility between versions and ALL site modules will need
> to be reinstalled. At the very least, extend -Dextras to support
> pulling the list from a file and let the admin figure out how to fill
> the file.
> How about
> with the file being a line oriented list of modules which should be
What's wrong with -Dextras=`some command here`? (well, maybe line
length and shell variable size limitations... but one can use bundles
to work around these)
> Plus we provide a script to extract the contents
> of perllocal.pod and let the admin edit it before running Configure.
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen