# from David Golden
# on Wednesday 28 January 2009 09:46:
>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.
I think none of the clients currently support the dynamic_config => 0
flag. If this flag is true (or missing), the META.yml requires &c are
defined as "unknowable" without running Build.PL. What is also missing
from the current process is to for Build.PL to write a MYMETA.yml based
on what it computed for the current machine.
>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.
I think this sort of thing will have good uses in the declarative form
(METAbefore.yml?), but I'm not sure about trying to fit it directly
into META.yml.
--Eric
--
software: a hypothetical exercise which happens to compile.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
