On 18.02.2013 12:52, Andy Parker wrote:
I think publishing this on the forge would be a great idea. It does leave open the question of what we should be doing with the things that are already in core. It is a shame to have them rot and force everyone to download another module to get working ssh_authorized_key management. My plan for slimming down puppet was to pull out types and providers to put them on the forge and then bundle some back in during packaging so that we still had a "batteries included" puppet installation. We still need to figure out how to do that in a manner that "just works".
Would it be enough to have a separate recommended modules package that installs default modules into a system location (/usr/share/puppet/modules) which is configured into the default module path?
Best Regards, David -- 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 post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
