Front page | perl.perl5.porters |
Postings from August 2001
From: Horsley Tom
August 1, 2001 04:43
Message ID: 707033366258D411BC9C00805F0D91071B1CDA@exchange.ccur.com
> 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.
Unless CPAN has gotten a lot smarter, it seems unlikely that any
automation will work. I've been rebuilding perl plus all installed
modules from scratch on each major release for the last several
releases, and so far, some special case has always cropped up
on every build. The latest version of ABC now depends on module X
(but it didn't before), and will even break if you have module Y
(now obsolete) installed, etc., etc. I gave up trying to automate
it a long time ago.
If CPAN recorded the module dependencies so it could fetch everything
needed and install them in the right order, and if it also recorded
modules now marked as deprecated, so it could *avoid* fetching them
(even if they are in perllocal.pod), then maybe automation would
stand a chance, but don't bet on it (in fact, the last time I built
everything, I discovered that one of the modules I installed had
a dependency that only showed up in "make test" - you could install
without it, but you couldn't test without it - thats the sort of
thing an automated system is bound to miss).
I don't want to rain on the automation parade, I just want to point
out it is non-trivial to get right :-).