libfoo<major> (was: Incoming: directfb soname problems)

[Axel Thimm]

On Sat, May 13, 2006 at 09:44:48PM +0300, Ville Skyttä wrote:
> On Sat, 2006-05-13 at 10:35 -0700, Thomas Vander Stichele wrote:
> 
> > Log Message:
> > new upstream release
> 
> ...which due to the soname change in it, will break stuff and leave yum
> users without all updates until they figure out what repo they need to
> temporarily disable in case they're using ones that have dependent
> packages.
> 
> libdirect-0.9.so.24   -> libdirect-0.9.so.25
> libdirectfb-0.9.so.24 -> libdirectfb-0.9.so.25
> libfusion-0.9.so.24   -> libfusion-0.9.so.25

Maybe it's time to think about packaging so into their separate
libfoo<major> subpackages like Debian/Mandrake/ATrpms are doing? This
always ensures forward and backward compatibility at the cost of dead
libfoo<major> packages lying around.

But unused libfoo<major> packages can be auto-cleaned should that be
the only issue against them. And the management overhead can also be
nicely reduced. If there is interest to look into that route I can
elaborate more on this.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-extras-list/attachments/20060514/bf0e58df/attachment.sig>