On 1/14/10 7:05 AM, Jewels wrote:
I searched through the archives and can't seem to find this. I have a
package that has rpms for install, and i am able to do that, not a
problem.
I am looking for a way to ensure it is upgraded?
I have version 1.0 installed and want 2.5.3 installed on all systems.
so *IF* you can't upgrade to 2.5.3 until you have 2.0, then 2.5 in
place, how can I put in a recipe that says - install this, then that
then that based on what is currently installed?
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
--
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.
