On Monday, January 13, 2014 7:13:20 PM UTC-6, Dustin J. Mitchell wrote: > > How about something as simple as a top-level "modules" directory in > the puppet source, which is installed separately and dynamically > appended to the modulepath at runtime? That avoids any problems for > users who set modulepath, allows modules in users' modulepaths to > override the built-in modules, and doesn't use the inaccurate name > "contrib". It also makes it easy to move modules in and out of core. > >
I like the idea of a system modulepath wherein reside modules that are accounted in some way part of Puppet itself, with that being appended automatically to the user modulepath. I think that will make the change fairly transparent to users, even if it occurs over several releases. That would also make it convenient to package the tier-2 stuff separately from the Puppet core, if so desired, and I think it would be easy to maintain (as much so as any alternative I can think of, anyway). 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/e6e6170a-3bdd-4b54-88ef-aa2d76b2c88b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
