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

[Angelo Naselli]

Alle martedì 8 maggio 2007, Gilles Caulier ha scritto:
> 2007/5/8, Angelo Naselli <anaselli at linux.it>:
> >
> > Alle martedì 8 maggio 2007, Angelo Naselli ha scritto:
> > > Alle martedì 8 maggio 2007, Achim Bohnet ha scritto:
> > > > On Tuesday, 8. May 2007, Angelo Naselli wrote:
> > > > > Alle martedì 8 maggio 2007, Achim Bohnet ha scritto:
> > > > > > On Sunday, 6. May 2007, Angelo Naselli wrote:
> > > > > > > SVN commit 661885 by anaselli:
> > > > > > >
> > > > > > > Release 0.1.4
> > > > > > > - fix libtools version-info
> > > > > >
> > > > > > Hi, Angelo,
> > > > > >
> > > > > > looks like it get fixed in the wrong way ;)
> > > > > >
> > > > > > When I build 0.1.4 pkgs and install them, digikam io slaves only
> > give errors like
> > > > > >
> > > > > > digikam: ERROR: : couldn't create slave : Unable to create
> > io-slave:
> > > > > > klauncher said: Error loading 'kio_digikamthumbnail'.
> > > > > >
> > > > > > Reinstalling 0.1.1 and digikam works again.
> > > > > >
> > > > > > Anyone else tried to run an app build with 0.1.1
> > > > > > to run with 0.1.4?
> > > > > hmmm are this comment the reason?
> > > > > (Depreciate: used internaly by digiKam core.)
> > > > >
> > > > > Gilles you changed a lot of methods from protected to private,
> > > > > I guess if that was the cause
> > > >
> > > >
> > > >
> > > > mhmm,  looking into .xsession-error shows:
> > > >
> > > > usr/lib/kde3/kio_digikamthumbnail.so: undefined symbol:
> > KExiv2Iface::KExiv2::getImageOrientation()
> > > >
> > > > if only this method is missing.  I would suggest to
> > > > just keep this method instead (make as depreacated)
> > > > and delay delay API backward break to a future release ;)
> > > Anyway it's a mess, since libkexiv2 is not used by digikam only.
> > >
> > > Suggestion?
> > Ok so it seems we missed the compatibility between 0.1.1 and 0.1.2
> > but we realized it after (e.g. > 0.1.3) that means all the releases
> > we've done till now are "broken". I suggest to change version info
> > to 2:1:0 anyway.
> > WDYT?
> >
> >
> > Angelo
> >
> 
> You want mean something like libkeviv2 0.1.4 using a version info like 2:1:0
> ?
> 
no libkexiv2 0.1.5 ;)

> There is no relation between the package release id and the version info of
> library ?
correct. And so it should be
cut from http://www.gnu.org/software/libtool/manual.html#Versioning
[...]
So, libtool library versions are described by three integers:
current
    The most recent interface number that this library implements.
revision
    The implementation number of the current interface.
age
    The difference between the newest and oldest interfaces that this 
    library implements. In other words, the library implements all the 
    interface numbers in the range from number current - age to current. 

If two libraries have identical current and age numbers, then the dynamic 
linker chooses the library with the greater revision number.  
[...]
To have a relation we should introduce release number into name, but that,
you know, breaks binary compatibility...

Anyway could someone test if we can have a broken compatibility with the
0.1.1 only?
Between a crying time, followed by Ester's lunch, and another, I've taken 
a look at our packages:
Vers. - Rev.Tag- 
0.1.0 - 632646 - 0:1:0
0.1.1 - 636958 - 0:2:0
0.1.2 - 651677 - 1:0:1 < API changed (but i thought back compatible)
0.1.3 - 661379 - 1:0:1 < Wrong: API changed 
0.1.4 - 661885 - 2:0:2 < the right one could have been 2:0:1 if 
                         compatible with 0.1.2
So fixing release should be
0.1.5 - XXXXXX - 2:1:1 if back compatible with 0.1.2 2:1:0 otherwise.

Col can you test the binary compatibility in cooker? I mean IIRC there
was 0.1.2 in it now you upgraded to 0.1.4 digikam should start correctly.

TIA,
	Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20070508/4291237c/attachment.pgp