On Wed, Jan 25, 2012 at 5:25 PM, Ashley Penney <apen...@gmail.com> wrote:
> > All I know is that telling users "If you download 5 modules from puppet > forge > make sure you go through them all, extract any duplicating resources into > random modules that exist purely to allow you to realize packages" instead > leads > to a really bad user experience. > Absolutely. We're aware this is a big limitation for great collaboration on module content, and it needs to be addressed. Don't you think it makes more sense to make that part of module metadata rather than trying to do it inside all your manifests? If we have: * puppet module tool supporting dependencies and generating module metadata * classes not loading if their dependencies aren't satisfied (or at the least big warnings) do we really need defined()? -- Nigel Kersten Product Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
