On Wed, Feb 3, 2010 at 5:52 AM, <ja...@lovedthanlost.net> wrote: > On 3 February 2010 21:04, Julian Simpson <simpsonjul...@gmail.com> wrote: >>>> >>>> Can we start by grafting together everyone's modules and trying to >>>> namespace them? >> >> Has there been any discussion of bundling some common modules in the >> puppet distribution? It might help people get up to speed faster. >> > > I don't think we'd want to bundle modules into core - let's keep that lean > and mean
Yes. It won't be in the core. - I do think it'd be good to bundle the capability of pull common > modules into a Puppet installation. > > Something like a rake task (or perhaps in the Dashboard). > > $ rake pull apache We'll do something to make it easy, but I don't like the idea of exposing rake (a Ruby build tool) as part of our tool suite -- we don't want to be very Ruby centric, and also Rake isn't really great at option parsing and becoming an application, should we want to grow into that. We should probably have command line tools for stuff like this, however simple, but we'll see when we get there. Let's get this going and then see what software we needs as it goes. No need to design up-front on the list. For purposes of full disclosure, I don't expect to start this for several weeks, so look for something then, and then we can start looking at the repo and seeing what it needs and what folks think we should change. I want to roll up some of Teyo's modules best practices into the start of this, and then we'll have something to hang new work on. --Michael -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
