[Kde-imaging] libkexiv2: breaks backward compatitiliby? WAS: extragear/libs/libkexiv2

[Achim Bohnet]

On Wednesday, 9. May 2007, Colin Guthrie wrote:
> Angelo Naselli wrote:
> >> Regardless it will mean we can rebuild the dependant apps and everything
> >> will eventually work. Is this the desired effect?
> 
> > Yep, unfortunately it is. And since we have that problem in cooker we can di that
> > without care, but this problem makes me thinking we should pay attention next
> > time to avoid that...
> 
> Yeah I guess. Easy to slip through the net tho'.
> 
> Gimme a shout either here or via mail or via cooker ML if you want me to
> officially release 0.1.5 to cooker and do the rebuilds. Happy to do so.
> 
> One question tho', should I bump the major in the package? It would make
> it libkexiv21-0.1.5 (as opposed to current libkexiv20-0.1.4) It is my
> understanding that libkexiv2.so.0 is major 0 and libkexiv2.so.1 is major
> 1 but perhaps my understanding here is not quite complete here ;)

Use libkexiv2-1.    As upstream changed to version info it
makes not sense to include tarball version in the pkgs.

As long as libkexiv2 does not change the soname major
again libkexiv2-1.   After next backward compatibility
break we'll get libkexiv2-2, the -3 etc.

Achim
> 
> Col.
> 
> _______________________________________________
> Kde-imaging mailing list
> Kde-imaging at kde.org
> https://mail.kde.org/mailman/listinfo/kde-imaging
> 
> 



-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy at lion.austin.ibm.com