On 10/08/2012 09:21 PM, Jeff McCune wrote:
I hope this helps and thank you again for reporting this issue,
I think the easiest way of handling this issue is to have different
repositories for different versions of puppet.
So for example yum/rhel-compatible distros would have
* 'puppet26-release-6-6'
for puppet 2.6
* 'puppet27-release-6-6'
for puppet 2.7
* 'puppet30-release-6-6'
for puppet 3.0
That way, user can add for example repo 27 and not worry about it. When
one decides to upgrade, it can simply replace puppet27-release with
puppet30-release, which would provide newer version of packages (with
the same name) which offers seamless upgrade to latest and greatest.
I surely would not like to see all versions of puppet in same repository
but with different names (like puppet26, puppet27, puppet30), cause
that's not the purpose of version-in-the-name naming scheme - and it
makes upgrades impossible. One would have to remove old version first
and then install new version, and I surely would not want to do that on
hundreds of machines :(
--
Jakov Sosic
www.srce.unizg.hr
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@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.
