On Fri, Jan 10, 2014 at 10:17 AM, Ashley Penney <apen...@gmail.com> wrote:
> I'm late to the party but I want to throw my support behind Daniel's plan > to move all tier2 stuff into modules, right from the start, and ship known > tested versions with Puppet. > Even later to the party, but I agree :) The alternative of a contrib directory could muddy the waters so that there were 3 locations a given type/provider could land (core/contrib/module), when the current 2 locations (core/module) suffice. Easy to imagine extra bike-shedding on where something lands and/or the contrib directory becoming a failed experiment wasteland. However, one question I have about shipping modules with puppet as discussed in this thread: are people thinking this means modules pre-installed in /usr/share/puppet/modules, or that the packaging step would merge/patch the tier2 modules into puppet proper? If the former, is that overly disruptive to sites that specify modulepath? If the latter, does that complicate sites that want to upgrade one of the packaged-in modules using pmt? I haven't thought this through, so there may be a perfectly simple answer. Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014, September 23-24 in San Francisco* - http://bit.ly/pupconf14 Register now and save 40%! Offer expires January 31st. -- 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/CALsUZFG3zLXi1eEKpCNo4hP4jdNKXTyUZodVztpskTb-p5vdqw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
