Issue #2780 has been updated by Luke Kanies. Status changed from Needs design decision to Rejected
I actually like the idea, but I think Brice is right that a definition is probably the right approach for now. I think if we can come up with a clever way to specify when to do this automatic association and when not to, we should add it, but until that inspiration is reached leave it to people to figure out on their own. ---------------------------------------- Feature #2780: auto dependencies should be created between related packages, services, and files http://projects.reductivelabs.com/issues/2780 Author: Dan Bode Status: Rejected Priority: Normal Assigned to: Luke Kanies Category: Target version: Affected version: 0.25.1 Keywords: Branch: Feel free to file this under crazy request... I got this idea from Volcanes blog. The following pattern is very common: install package then config files which notify service and require package then start/enable services maybe there is a way to just build this into the language? maybe by creating auto dependencies between packages, services, and config files that have the same name/alias (which I guess wouldnt work if there was more than one config file) maybe this feature should be set as a metaparam (autodeppackage) that determines rather or not to create these dependencies. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
