On 13/05/16 13:01, Julien Pivotto wrote: >> Perhaps there's some middle ground, e.g. using alternatives to support >> multiple versions while trying to keep paths identical to existing >> packages? The SIG's packages couldn't then be installed alongside an >> EPEL package, but you might be able to install multiple versions from >> the SIG. It'd require extra work though. > > You mean, like having: > > - puppet RPM -> /usr/bin/puppet ; /etc/puppet > - puppet44 RPM -> /opt/xxx/bin/puppet44/puppet.conf ; /etc/../puppet44/puppet.conf I mean having: - puppet43 RPM -> /usr/bin/puppet43 - puppet44 RPM -> /usr/bin/puppet44 and using update-alternatives(8) or similar to symlink /usr/bin/puppet to puppet43 or 44, depending on the user's preference. Other packages such as JREs use this mechanism. I'm not sure what you'd do about confdir/vardir in the example of Puppet. -- Dominic Cleal dominic at cleal.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20160513/5a20d37b/attachment-0008.sig>