Issue #4067 has been updated by Nigel Kersten. Assignee deleted (Jesse Wolfe) Target version changed from Statler to Telly
Trevor, do you want to try and get some traction on the dev and/or user list with your proposal? ---------------------------------------- Feature #4067: Automatic dependency resolution for package managers. https://projects.puppetlabs.com/issues/4067 Author: Trevor Vaughan Status: Accepted Priority: Normal Assignee: Category: package Target version: Telly Affected Puppet version: development Keywords: package, auto-generation, graph Branch: Various parties have indicated that they would like Puppet to seamlessly integrate with the relevant package manager's dependency resolution ability if possible. Situation: If you have RPMs A and B, where B depends on A and Puppet objects that depend on one, or more, of the RPMs, then Puppet should automatically add relevant ordering objects to properly order the RPM dependencies. Example: RPM A RPM B B -> A package { "B": ensure => 'latest' } file { "foo": require => Package['B'] } Should this manifest be activated, Puppet should automatically, generate an internal dependency from B to A and insert it into the dependency graph. This is an obviously contrived example, but there are situations where you would want this type of thing to happen for more complex scenarios. -- 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://projects.puppetlabs.com/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.
