Not really, this give me a list of packages that are installed by all classes recursively, but what if someone decide to remove some package from some class that the tool labs classes are inherited from?
I think that only logical way of maintaining such a list would be to make it by hand and ensure that all packages on such a list are somewhere included (in some class). But I don't really think that anybody cares, hence almost no responses to this... Tool labs appear to me to be pretty much random when it comes to sw support... somewhere some stuff works, somewhere it doesn't... On Tue, Nov 12, 2013 at 9:31 AM, Federico Leva (Nemo) <[email protected]> wrote: > Some time ago, the answer was negative: > https://groups.google.com/forum/#!topic/puppet-users/ovyh5zA7Wkc > Now there is: > https://docs.puppetlabs.com/man/resource.html > http://stackoverflow.com/questions/17056801/auto-generate-puppet-manifests > http://serverfault.com/questions/338536/puppet-get-list-of-packages-and-versions > So you just need a loop of "puppet resource package --host" and comm -12, it > would seem. > > Nemo > > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l _______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
