On Thursday, November 20, 2014 9:38:35 AM UTC-6, Erik Dalén wrote: > > > > On Wed Nov 19 2014 at 8:36:46 PM Eric Sorenson <eric.s...@puppetlabs.com > <javascript:>> wrote: > >> >> >> On Nov 19, 2014, at 11:20 AM, Trevor Vaughan <tvau...@onyxpoint.com >> <javascript:>> wrote: >> >> > Hmm...Facter and MCollective not being independently upgradable isn't >> super exciting. >> >> >> If any one of the main constituent projects having a release would cause >> a new AIO to come out, is that the right cycle? >> > > > >> >> (Do you currently always track the latest package of the Puppet-related >> projects you use?) >> > > generally we don't, but almost. > Seems a bit odd to me to not be able to upgrade puppetdb, facter or > mcollective independently of puppet though. > > And we would likely need to install things into that ruby env anyway. So > why not have the ruby env as one package and the other packages depend on > that and install things into it? > >
And instead of an AIO packages, it would be possible in such a scheme to release dependency-only packages (aka metapackages, virtual packages) that describe complete collections of components without actually containing them. That would facilitate whole-suite installation upgrade without unduly interfering with installing or upgrading individual components. Done right, it might also provide a mechanism to determine whether a blessed combination of components was installed, *vs*. a possibly-mismatched hodge podge. John -- 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/38c49330-9d5b-45ef-98d3-29ee3128dccb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
