On Wed, August 26, 2009 3:23 pm, David Cantrell wrote:
> Terribly hard to measure, but I'd imagine that almost no authors have
> up-to-date versions of:
> Module::Build
> Module::Install
> ExtUtils::MakeMaker
> CPAN.pm
>
> just like they don't have up-to-date versions of any other stable module
> that *appears* to Just Work, such as DBI. I know that *I* don't - my
> toolchain is only mostly up-to-date on my testing machines.
>
> Perhaps CPAN.pm (and CPANPLUS) could add a way of checking for updated
> toolchain-ish modules on startup. Simply compare version numbers of
> what you've got against what's in the CPAN index files. There's no
> privacy concerns as the files are already available on the user's
> machine. Have it warn loudly if you've got old versions of tools.
>
> I'd be happy to add this to my To-do list if the maintainers think it's
> a good idea.
You mean something like the 'o' (CPANPLUS) or 'r' (CPAN) commands?
Although it looks like CPAN now has an 'upgrade' command, which I'd love
to see in CPANPLUS. ('Just go try to update everything that's got
upgrades, don't make me go through the list.' :) )
Daniel T. Staal
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
