So to come back to the original topic of the other thread, I want to lay out why I think we need this after all.
Assuming that most authors rely on M::B or EU::MM or M::I to create their META.yml, the result is that the META.yml requirements are specific to the authors system. If, for example, some requirement should be pulled in for a particular operating system or if a particular external library is available, then if those conditions are met for the author, they'll show up in META.yml. In other words, META.yml as generated by the author now is really just the authors MYMETA.yml. That seems less than ideal. Comparing the delta between META.yml and MYMETA.yml will only tell us the difference between the author's MYMETA.yml and anyone else's MYMETA.yml. A "maybe_requires" could be used to differentiate these more effectively. Programatically, it would probably need to be something like this: maybe_requires( $module, $condition ); Then $module would get put in maybe_requires in META.yml, but in requires in MYMETA.yml if $condition is true. -- David
