Front page | perl.perl5.porters |
Postings from July 2001
Re: perl@11523
Thread Previous
|
Thread Next
From:
John Peacock
Date:
July 31, 2001 13:38
Subject:
Re: perl@11523
Message ID:
3B671746.C19E457A@rowman.com
Jarkko Hietaniemi wrote:
>
> On Tue, Jul 31, 2001 at 02:45:08PM -0400, John Peacock wrote:
> > So now, all I need to do is write a script to walk through the
> > existing perllocal.pod and grab one instance of each locally installed
> > module and then pass that as a list to Configure. OR, should I patch
> > Configure to do that for me when I type -Dextras=perllocal???
>
> I don't think that Configure should do such things automatically.
> (How would it know which perllocal to scan?)
> But an external script, sure. (You might also consider using
> CPAN.pm to do the scanning.)
It is not doing it automatically; I asked for it. I guess my point
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
-Dextras=/usr/local/lib/perl5/5.6.1/cygwin/perllocal.pod
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
-Dextrasfile=here_is_my_listing
with the file being a line oriented list of modules which should be
fetched/installed. Plus we provide a script to extract the contents
of perllocal.pod and let the admin edit it before running Configure.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
Thread Previous
|
Thread Next