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.
  • What are these indirect dependencies of which you speak?

    • Your module requires Foo, so you add Foo as a dependency, this is normal stuff. Foo requires Bar and Baz, which your module does not directly depend on. The suggestion therefore is to add Bar and Baz to your module's list of dependencies in it's META.yml file for example. That way when the automated CPAN tests are run, the version of Bar and Baz will be reported as well as Foo.

      In my case XML::RSS:Tools uses Test::Warn in some tests. Test::Warn uses Sub::Uplevel. The problem was that Test::Warn was not worki

      --
      -- "It's not magic, it's work..."
      • Why does your distribution have to make up for someone else's broken distribution?

        Is there not already a test for PAUSE or CPANTS to test that a distribution is "broken" because it doesn't specify its dependencies?

        • It is not broken. Test::Warn depends on Sub::Uplevel. Test::Warn 0.10 dies with new version of Sub::Uplevel (when it was upgraded after install of Test::Warn). It is not possible to modify old versions of Test::Warn to require old Sub::Uplevel. New version of Test::Warn works with both old and new version of Sub::Uplevel.

          I already thought about this situation. There is a field in META.yml to specify conflicts, but none supports it.