Slash Boxes
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.
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 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, could check and force-upgrade. I've had this conversation with Ken, and there's an RT ticket in the 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't change the fact that right not it does have that problem.

        Module::Install has suffered from the same problem as Module::Build in regards to having to incrementally release all those modules. It was hyped too heavily, too early and too often. Both M:I and M:B are incomplete installers with significant problems to be resolved.

        As for getting modules upgraded, the same rules we have always had apply. When someone needs it, they ask the author, or they take co-maint and do a release themselves.

        The number of modules existing is indeed too high.

        But I don't recommend people use EITHER M:I or M:B until they reach version 1.00 and become more stable. So I continue to only recommend M:I only in the specific case the author will be doing regular releases.

        Fortunately, M:I is trying to avoid hyping any more until the major problems have been removed and it has been tested properly.
        • How are the user's supposed to know to upgrade Module::Build.

          If only there were some way CPAN or CPANPLUS could know about dependencies during an installation... yeah, that'd be SWEET.

          • I find that not only a cheap shot, but a rediculous statement coming from somebody that doesn't actually know how the mechanism by which CPAN learns about dependencies during an installation. Both of them.

            Until you learn how the Perl installation process works, it's pointless to continue this too and fro.