On Oct 10, 2010, at 8:48 AM, Nicholas Clark wrote:
On Thu, Oct 07, 2010 at 02:01:13PM -0500, Craig A. Berry wrote:
In the core, utils/cpan.PL is simply a wrapper that sucks in cpan/
CPAN/
scripts/cpan, puts $Config{startperl} at the beginning, and writes it
back out. There are a bunch of these that all have identical code
except for the name of the utility, so one obvious rationalization
would be to put that code in one script and have it work through a
list of utilities to be generated.
Agree. But
1: I remember having to alter those paths when modules moved from
ext/ to
dist/ or cpan/, and it felt like makework, so I wanted to kill it
properly
2: When building these modules from a CPAN download,
ExtUtils::MakeMaker
already has to do all this extraction work , shebang rewriting,
running
pl2bat, so surely it could do it when the modules are in the core
which, I felt, would remove even more code from core :-)
[Clearly this doesn't work if it hasn unresolved a bug in this area
for VMS]
With the pod*PL extractors, by moving them all out of pod/
(including creating
ext/Pod-HTML for Pod::Html, which isn't dual-life), it let me remove
several
rules from the various Makefiles. It might be that if we can move
all of
utils/ into its modules, or into ext/utils, we can further simplify
the top
level Makefiles, and let make_ext.pl and ExtUtils::MakeMaker do the
work.
fixin() and the various *.PL scripts in utils have two different
understandings of what $Config{startperl} is and how to use it.
The .PL scripts have it right as far as VMS is concerned, so it looks
like we need to fix fixin().
This would be useful.
This is now (at long last) done:
http://perl5.git.perl.org/perl.git/commitdiff/613e98e463d92e7eb6bfa6d25de65632ece7d50f
http://perl5.git.perl.org/perl.git/commitdiff/5844a3edbd3499c6a146436e1d7ec0648feacb5b
Sorry for the slow follow-up.
________________________________________
Craig A. Berry
mailto:craigbe...@mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
