Adam Kennedy wrote:
It's part of the 1.2 spec:
<http://module-build.sourceforge.net/META-spec-v1.2.html#resources>
On the subject of spec changes, I was wondering what people thought of
changing the dynamic_config option to become static_config or
static_metadata.
It seems silly that the default is 1, and thus the only time you need to
provide information is when you say
dynamic_config(0);
I've CC'd this to the module-build mailing list as it's probably a
better place to ask.
I have to admit that I'm not totally sure what this option is for. There
are a number of problems it could be intended to solve, but I'm not sure
which one(s).
1) For automated builders/testers, it could indicate that a module
requires user intervention. Eg. it queries the user for input during
install.
2) The dependencies listed in META.yml are not static. Maybe a Win32::*
module is required only when run under Windows, but is not listed in
META.yml because there is currently no way to express conditional
dependencies.
3) The description in the spec would seem to imply that a static config
indicates that module can be installed without the builder (i.e.
Module::Build)), that the modules could simply be copied into the proper
folders by any tool. This would mean any module with with XS or compiled
code as well as anything under (1) and (2) above are dynamic?
Randy.
