RFC: adding a temporary, non-BC gauranteed, 'private' library .. where?

Sune Vuorela nospam at vuorela.dk
Thu Apr 23 19:47:16 BST 2009

On 2009-04-23, Andreas Pakulat <apaku at gmx.de> wrote:
> On 23.04.09 18:09:58, Sune Vuorela wrote:
>> On 2009-04-23, Andreas Pakulat <apaku at gmx.de> wrote:
>> > BTW, I'm not saying the above idea is good (in fact I think its the
>> > worst solution), but I'd like to understand the bad downsides for you
>> > packagers when one of the libraries kdelibs changes its SONAME. 
>> Because we have based our packaging on your (KDE's) earlier promises tha
>> kdelibs was backwards binary compatible thru all of kde4.x
> We're guaranteeing that for the public libraries of kdelibs, not for
> anything thats considered private.

Once you install the headers, it is a public library.


More information about the kde-core-devel mailing list