RFC: adding a temporary, non-BC gauranteed, 'private' library .. where?
apaku at gmx.de
Thu Apr 23 19:36:08 BST 2009
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.
You will be a winner today. Pick a fight with a four-year-old.
More information about the kde-core-devel