Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... Module::Build doesn't have a method for ensuring users upgrade.
    use Module::Build '0.xx';

    Alternately, stick the dependency in build_requires.

    • Even users only need to upgrade their M::B when they’re about to install something. And CPAN.pm could check if there is an upgrade to M::B and suggest doing it just like what it already does for updates to itself.

      Seems much more tenable than the M::I model to me.

      I mean, look at that list – good luck getting all 83 authors to push out 469 new releases total, just to fix their installers. And that’s now that M::I is relatively new – what will the situation look like when the CPAN i

      • How are the user's supposed to know to upgrade Module::Build.

        Installers should always assume the user is completely clueless, or doesn't even exist because they've been replaced by a small shell script.

        Yes, CPAN.pm could check and force-upgrade. I've had this conversation with Ken, and there's an RT ticket in the CPAN.pm queue that says "auto-upgrade a specific set of named modules". But it DOESN'T.

        And no amount of handwaving about how other people (users or Andreas) could fix Module::Build's problem doesn'