> Lets dumb it down. How can I ENSURE that EVERYTHING from module A is > implemented before ANYTHING from module B?
That's roughly like asking: How can I ensure that no code from jar file A depends on jar file B? It's really up to the individual classes inside the jar files to behave the way you want. I'd like to make a proposal around module metadata, so that you could declare things like: - this module depends on others - this module works for this list of $operatingsystems - this module uses this sysadmin strategy J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
