Scott Smith wrote:
That's pretty complex. It might not work, but I would try defining
package resources for each version and have each successive version
require the previous. RPM should be smart enough to handle it, so give
it a shot!
-scott
I'm skeptical that this would work. And I would expect the final result
to be:
Upgrade to/Install v2
Upgrade to 2.5
Upgrade to 2.5.3
And on subsequent runs you'll get errors about not being able to
downgrade to 2, and not being able to run the next resources because of
failed dependencies.
If it doesn't work (I hope for your sake that it works) the only
solution I can see involves creating a fact to get the current state and
version of the package. And then based on that with some ifs get the
required definitions in place...
Silviu
--
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.
