Hello, On Fri, Jan 27, 2012 at 15:20, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: > how I see need for > explicit module dependencies and a system that can automatically > download required modules from the forge. I can see this supplementing > your idea of constraints nicely, but without it, downloading modules > could quickly become a nightmare for users. There's something else we need to think about here. Some modules have a soft/conditional requirement for other modules. What I mean is that if you don't use certain parts of a module, you don't need the module that that part of the code refers to. the only decent way I can come up with to solve that is to use what for instance in C is done with #IFDEF. That way the module could just ignore modules that it doesn't _really_ require.
I for instance have modules that allow you to use different backends for monitoring or backups. If requirements were done automatically based on the whole module, it would need a myriad of other modules, only one of which is ever used. cheers, -- Walter Heck -- follow @walterheck on twitter to see what I'm up to! -- Check out my new startup: Server Monitoring as a Service @ http://tribily.com Follow @tribily on Twitter and/or 'Like' our Facebook page at http://www.facebook.com/tribily -- 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.
