[Pkg-kde-extras] Re: kipi/kexif libstdc++ transition

[Mark Purcell]

On Wednesday 16 November 2005 22:09, Achim Bohnet wrote:
[...]
> > Well the current situation is like this:
> > hoary -> libkexif0, libkexif0-dev
> > breezy -> libkexif1, libkexif1-dev
> > dapper -> libkexif1-dev, libkexif1c2
> > Sarge -> libkexif1, libkexif1-dev
> > Etch/ Sid -> libkexif1-dev, libkexif1c2
> >
> > I suppose if we can come up with a schema which doesn't conflict with any
> > of the above then it should be good to go.  But not that libkexif1 is not
> > an option as it has already been used by breezy & sarge, even though that
> > is what the correct solution should be.
>
> libkexif1 is the one ;)  Sid/Etch & Dapper does not count because there are
> in flux.  So we eventually we will have libexif1 everywhere.  (Ditto for
> libkipi0c2 -> libkipi0)

We can't use libkexif1, otherwise packages from sid/ dapper, which have gone 
through the C++ tranisition will attempt to use the libkexif1 from sarge/ 
breezy, which won't work..

> P.S. With the next API aka soname change I also ponder if
> this will be libXXX<soname+1>-dev as suggested in the library
> pkging guide or libXXX-dev as favored by most(?) DDs.

It's really up to us whatever we want and think is a good thing.

Mark