Hi,
I've run into the problem of conflicting dependencies several times: for
example, quite a few public modules use different apache module
implementations. While it is often to fix those modules locally to use
the preferred version, it is cumbersome and error prone.
I was wondering whether it would be possible to have the modules
installed not to $modulepath/$modulename, but to
$modulepath/$author-$modulename and have the master pick up the right
classes/defines, depending on the information in metadata.json,
similarly to how bundler sets up gems.
Of course, that doesn't fix configurations where multiple different
versions of the same module name are required on the same node, but
that's a different quality of problem, that can be quite easily fixed by
using separate nodes, without modifying the modules themselves.
Is this something that would be possible/feasible?
Regards, David
--
* Always looking for people I can help with awesome projects *
Twitter: @dev_el_ops G+: https://plus.google.com/+DavidSchmitt
Blog: http://club.black.co.at/log/
LinkedIn: http://at.linkedin.com/in/davidschmitt
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/5476D9A2.7020107%40dasz.at.
For more options, visit https://groups.google.com/d/optout.
