Jos Vos wrote:
> A question to packagers: what would you think of a policy to add
the
> library soname in package libraries ? [...]
If I understand your question correct: this is all done automatically
when rpm calculates the provides/requires (using the "find-provides"
script) when building the package.
Look at the package you generated with "rpm -qp --provides package.rpm"
and see what it shows.
$ rpm -qp --provides libkexif-0.2.1-0.fdr.1.i386.rpm
libkexif.so.1
libkexif = 0:0.2.1-0.fdr.1
$ sudo rpm -Uvh libkexif-0.2.1-0.fdr.1.i386.rpm
libkexif-devel-0.2.1-0.fdr.1.i386.rpm
erreur: Dépendances requises:
libkexif.so.0 est nécessaire pour (déjà installé)
kipi-plugins-0.1-0.fdr.0.1.beta1
libkexif.so.0 est nécessaire pour (déjà installé)
digikam-0.7-0.fdr.1
libkexif.so.0 est nécessaire pour (déjà installé)
showimg-0.9.4.1-0.fdr.1.2
My point is that if the rpm name contained the soname, version 0.1 and
version 0.2 could be installed at the same time, and I would not have to
update all the packages depending on it immediatly. With only 3
applications, it's not a very big problem, but it could be a lot worse with
a more important library.
Aurélien
--
http://gauret.free.fr ~~~~ Jabber : gauret(a)amessage.info
Passwords are like underwear. You shouldn't leave them out where people
can see them. You should change them regularly. And you shouldn't loan
them out to strangers.