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.
  • autobundle should be the way to go. Dependencies are resolved in
    two ways: because the old installation already had the
    dependencies resolved, so you have all required modules also in
    the new installation, and because anyway makes sure that
    dependencies are always resolved.

    But there's one gotcha: it can happen that left-over modules from
    older versions of large distribution may cause the old
    distribution to be installed again. Usually one protects himself
    by using UNINST=1 while installing distributions, b

    • Thank you all who answered. Yes, autobundle is an answer to the basic feature request.

      For my production stuff, installing extra crap is undesired. But that's not what I'm talking about here.

      I'm more focused on my development stuff. Here, I not only want hard dependencies, like CPAN handles, but also soft dependencies.

      For example, Test::Critic, as I mentioned, installs just fine without Test::Deep. So, as I understand autobundle's workings (now that I'm looking at it), it will always install Test::Critic

      • So if I understand you correctly, then you want support for the "recommends" field in META.yml? As far as I know cannot handle "recommends" (yet). But it shouldn't be to hard to implement it.

        • That is probably accurate, as far as it goes.  :)

          That having been said, I don't see the recommends as 100% synonymous with the concept.  Module A can recommend module B because it is complementary to module A, even though there's no code interactions, and no tests which one can do for the other.  I'm not interested in that kind of a relationship, as far as this rebuilding goes.

          Specifically, what I'm looking for, for a test-happy build, is the ability to install all test dependencies - both hard and 'recommends' - before running the tests for a new module.  If those test dependencies produce a loop, then I'd like the test report for the modules to not be issued until both modules are installed, and then re-run the tests.  (Note: if both tests then failed, I'd probably consider this another form of na.)

          Disclaimer: I'm being idealistic and stuff here.  I've only just installed CPAN::Reporter, and there's a lot about cpantesters I don't yet know.  I haven't looked at the code, and I don't know how complicated this would be to code.  I don't expect all of this stuff to be implemented any time soon - since actually starting to communicate with and learn more about the rest of the Perl community, I'm really impressed with how much of the stuff I'd like to see coded already *is* coded, or already has some vestigial existence.