Dustin Oprea wrote:
In the scenerio where a file (say libssl.so.5) is provided by a package, but the next version of the same-series of the package provides a 'libssl.so.6' instead, as is common, how can we maintain the previous file to satisfy all of those packages that require that specific version, whilst at the same time upgrading to install all newer files?
You could do something like 'rpm -i --replacefiles'. That would keep the old version as well as the new, and also install the variant from the new where both version have the same files.
But this does not seem like an entirely "clean" way of going about it. You probably want to avoid having different versions of the same package in most cases.
I believe the common way to address this issue is simply to repackage the "old" .so file(s) in a separate, differently named, rpm that does not contain additional support files (thos go in the main package.) For instance, Fedora Core 3 had openssl-0.9.7a-40.i386.rpm and openssl096b-0.9.6b-19.i386.rpm. The former was the "proper" package with documentation, config files etc. and the latest version of the libs. The former just contained older versions of the DSOs + some versions specific doc files.
Now go find the spec files etc. to figure out how exactly they maintain the packages...
Is this a stable thing to do? Dustin
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
