How to avoid conflicts when forking a module?
I want to use a module (say
forge/module 4.1.0) from puppetforge, but it lacks some features I need.
Other modules by the same publisher I want to use depend on this module.
When using librarian-puppet 1.0.9 (puppet master/agent version is 3.6.2) to create my $modulesdir, how can I ensure that my modified version is pulled without breaking other modules?
Things I've tried:
corpobviously doesn't work because of the other puppetforge module's dependencies.
- Changing all the modules I need to avoid the clash seems like too much of a hassle.
- Appending a site-specific suffix like
-corp0didn't work, despite librarian-puppet printing an error message mentioning http://semver.org and the rules there suggest that this is acceptable. Also, it's not clear how depending on that would work according to the
My solution was to specify a version number like
4.99.0 and depend on that in the Puppetfile.
Apart from the obvious answer of trying to get my changes accepted by upstream, what's the canonical answer to managing a customized version of a such a module with librarian-puppet?