Front page | perl.perl5.porters |
Postings from January 2007
Re: New release ?
Thread Previous
|
Thread Next
From:
Jos Boumans
Date:
January 7, 2007 02:11
Subject:
Re: New release ?
Message ID:
6855.80.127.35.68.1168164657.squirrel@webmail.xs4all.nl
On Sun, Jan 07, 2007 at 02:12:38PM +1100, Adam Kennedy wrote:
> I have two items left pre-5.10.0.
>
> Firstly, replacing that mishmash of Module::Load Module::Loaded etc with
> some sort of Package::Util module that links to the Perl internals for
> things like class->filename etc
Replacing them would also mean replacing their use in CPANPLUS and
half a dozen other modules that I've sent patches for to integrate.
Even though not impossible, this would introduce a new round of patches
to the core and stability testing etc. The modules that have been added
now have been 'in the wild' for a long time, no (serious) bug reports,
etc.
I'll leave the call up to the pumpking -- I understand your PoV for
at least aesthetic reasons, but there is a significant practical
overhead should we choose to do this.
> Secondly, and more critical I would REALLY like to address the toolchain
> upgrade problem.
[...]
> I think that whatever toolchain modules we put in the core MUST be able
> to self-upgrade so that in 2 or 3 years time you will actually be able
> to sit down at a 5.10.0 box and say "install Module::Foo" and it will
> Just Work.
>
> Now, exactly how to do it?
The development release of CPANPLUS knows how to selfupdate, and CPAN.pm
can already do it too. For CPANPLUS, this just upgrades the core and
possibly dependencies (if you ask it too), but not something that's not
explicitly used by CPANPLUS (like Time::Hires for example).
Some details here:
http://search.cpan.org/src/KANE/CPANPLUS-0.77_02/ChangeLog
I'm not sure if this is what you had in mind?
> I'd suggest that at the very least the version of CPAN and CPANPLUS in
> the core need to be able to be instructed from the server if there are
> new critical compulsory upgrades, for a limited set of modules.
>
> How exactly? I'm not sure, but a simple config file with a list of
> minimum recommended and/or compulsory toolchain versions held in the
> CPAN somewhere would help a lot.
>
> CPAN(PLUS) could pull this file, check the local toolchain against the
> list, and upgrade itself before it starts installing modules.
I have a problem with 'mandatory', but this mechanism you describe
already exists. It's called 'Bundle::*' -- we could have a
bundle::perl::upgrades::($^X -v) for example that CPAN(PLUS) could check
for the user.
-- Jos
Thread Previous
|
Thread Next