Issue #4067 has been updated by Trevor Vaughan.
Well, the theory of execution was this: 1) Server passes compiled manifest to client 2) Client loads manifest into memory 3) Client executes all yumrepo/whatever statements 4) Client begins to execute 4a) All repo types are executed (no sense in doing them later) 5) Client searches tree for all 'package' objects (perhaps set these aside in compiled manifest as an object tree?) 5a) Client rebuilds execution tree based on known packages, links, and package tree 6) Execution starts from the top of the repo as usual. Alternatively: 1) Server compiles manifest and selects package types 2) Server sends package request to client 3) Client returns package tree to server 4) Server builds entire tree with in-memory package types and dependencies In both cases, similar package names are grouped. This means taking architectures, etc... into account. It *should* work but, then, I haven't had time to hack it, so what do I know :-P. ---------------------------------------- Feature #4067: Automatic dependency resolution for package managers. http://projects.puppetlabs.com/issues/4067 Author: Trevor Vaughan Status: Accepted Priority: Normal Assignee: Category: package Target version: Statler Affected 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.
