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.
  • Firstly, thanks for pointing out there is a discussion about something that is potentially of interest to the WHOLE of CPAN and not just a small subset. Wouldn't it be better to have a specialist list regarding META.yml specs, that discusses these sort of changes? A Module::Build list is not something I am going to sign up as I tear my hair out with MB at the best of times.

    When I first saw your post, I assumed this was part of the Module Authors list discussion a few weeks ago, but struggled to find the th

    • The main issue here is that META.yml is not authorative, with the exception of the configure_requires key.

      You need to run Makefile.PL in order to determine the configuration (and thus dependencies) for that host.

      Thus, META.yml is considered to be advisory only.

      New and useful keys in META.yml are those that are likely to be useful in an advisory context.

      Knowing the minimum Perl version meets this criteria, as useful things can be done by mapping dependencies at a graph level and working out which modules are blocking back-compatibility of their dependencies, etc etc.

      It's very common for Makefile.PL to do interesting and unusual things regarding search for libraries, so while somewhat interesting, the usefulness of a requires_library in an advisory context is somewhat reduced.