Oh right. Yes, of course, it *can* (and should!) be solved cleanly if you are in control of all involved modules. It gets hairy were third party modules enter the fray.
Cheers, Felix On 03/28/2014 04:32 PM, Peter Bukowinski wrote: > I do the same currently. I have a module that installs/updates an > in-house-developed scientific application with many os package (yum) and > python module (pip) dependencies. I recently wrote a second module for > another scientific application with overlapping dependencies and saw > duplicate resource declaration errors when I first tested it. > > My workaround was to pool the package requirements from both modules > into a separate module and simply include it in my application modules. > It sollved the issue, but nodes that only need one of the two > applications will get more packages than they require. I suppose I > should tag each package with the name of the application that requires > it and use virtual resources to only realize the necessary packages, but > I'm satisfied with the current solution since the overlap is pretty > significant. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53359C5D.5040102%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
