From kde-core-devel  Fri Apr 24 22:19:53 2009
From: Alex Merry <kde () randomguy3 ! me ! uk>
Date: Fri, 24 Apr 2009 22:19:53 +0000
To: kde-core-devel
Subject: Re: RFC v2: adding a temporary, non-BC gauranteed, 'private' library
Message-Id: <200904242320.03906.kde () randomguy3 ! me ! uk>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=124061169122689
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1810124.HyQzHq3Evr"

--nextPart1810124.HyQzHq3Evr
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Friday 24 April 2009 20:53:00 Friedrich W. H. Kossebau wrote:
> Vrendredi, le 24 avril 2009, =C3=A0 21:16, Kevin Krammer a =C3=A9crit:
> > Well, if you define the stability guarantee for your libs that way, then
> > you should probably stick to it.
> > I just thought you might not follow the stricter rules for platform
> > libraries. Usually application level APIs are far less stable.
>
> As written in another email, I had missed the lift of this stricter rules
> for non-platform libs a few month ago, so my assumptions regarding the
> oktetalibs were not up-to-date. :)

I understood that it was always the case that the BC guarantee only applied=
 to=20
kdelibs and kdepimlibs.  kdebase-workspace has certainly never bothered abo=
ut=20
binary compatibility of its libraries (except in so far as bumping the=20
SOVERSION when it is broken).

Alex


=2D-=20
Why have I got six monitors?  Because I haven't got room for eight.
  -- Terry Pratchett


--nextPart1810124.HyQzHq3Evr
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAknyOwkACgkQBRauKLutZ9BfxwCgnamb2EHSy/gfDdfpBuO74j3E
EDIAn0FS+1OEVFdWJb2bnQr9n/kond+C
=LMWi
-----END PGP SIGNATURE-----

--nextPart1810124.HyQzHq3Evr--