On Sep 8, 2014 2:21 PM, "Brett Swift" <[email protected]> wrote: > > why isn't puppetlabs_spec_helper installing dependencies of my dependencies? ... > but puppetlabs_spec_helper doesn't. <grumble grumble> > > I didn't see a ticket for this ontickets.puppetlabs.com. Is this a feature request, a defect, or pebcak ?
Assuming you're talking about modules installed with "forge_modules" (which I wrote the first cut of) instead of "repositories", I consciously added the flag to ignore dependencies with the PMT with the expectation that you should know what your dependencies are and be explicit about them. That said, I have found myself annoyed with having to remember to add all of the (>1)th-order dependencies, especially for our mass of internal modules. It also brings up the broader question of whether you really should need to track the transitive closure of your dependencies. Other packaging systems don't make you, so should you really have to here? It could be added as a configuration parameter, but then the next question is where should that be? A configuration section in .fixtures.yml? An environment variable? Then I get side-tracked thinking that maybe the name of .fixtures.yml itself should be selectable by environment variable so you could test with different combinations of versions of dependencies, etc. Wil -- 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/CAMmm3r77GwHzKxah8m0a0cr%3D%3DLnctCbK07Lmxct2-a%2BPTpUivw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
