in reply to Re^2: Wow! Painful upgrade to Perl 5.12
in thread Wow! Painful upgrade to Perl 5.12

Point would be to share pure perl modules as much as possible, and avoid duplicate or reinstall among various perl versions as far as possible.

How do you know those pure Perl modules have no XS dependencies, and how do you know those pure Perl modules and their dependencies work unmodified on newer versions of Perl 5?

  • Comment on Re^3: Wow! Painful upgrade to Perl 5.12

Replies are listed 'Best First'.
Re^4: Wow! Painful upgrade to Perl 5.12
by parv (Parson) on May 19, 2010 at 18:46 UTC

    I personally care about only of those pure perl (call it "pp") modules which would continue to work with changing supporting software to a large extent, barring API changes. I am under no illusion that pp modules would not need to be ever updated to follow supporting software. If a otherwise pp module follows very closely changes in supporting modules, then it could go in the "perl-verison" directory along with rest of the lot.

    Those concern are for later|never term, for me; I still do not know how to differentiate module type programmatically.

    Putting the issue other way, would this be workable (to avoid manual work of module installation via any method among package manager, cpan, "perl Makefile.PL", etc.) ...

    • programmatically generate list of modules in old version;
    • install new perl;
    • programmatically generate difference list from modules in new perl (in core, I suppose) & previous list;
    • install modules from the difference list

    ... ?

[reply]

      CPAN has an autobundle command for that purpose.

[reply]
[d/l]

In Section Meditations