Closed mmarseglia closed 9 years ago
@mmarseglia thanks for the PR! I think this is something I'd like to handle a little more elegantly. I originally opted for camptocamp's module because it had more downloads on the forge (not the best metric, but meh). I'd like to use the load_module_metadata
function once it's released in the stdlib (see: http://scienceofficersblog.blogspot.com/2015/08/inspecting-puppet-module-metadata.html) so we can support both modules. Any thoughts?
:+1: for inspection with load_module_metadata
load_module_metadata looks like a good solution. i also vote to use it and support both modules.
i have no preference for either camptocamp or puppet-community but i'm running into module dependency/conflicts. i'll end up using my fork until load_module_metadata can be implemented.
i'll close this PR. thank you for bringing that up.
I'd like to use another module to install/manage Wildfly but it utilizes puppet-community/archive. I also use the virtualbox module and unfortunately the two different archive modules are conflicting.
Any interest in switching from camptocamp to puppet-community/archive?