4.0 -> 4.1 binary compatibility

[Andreas Pakulat]

On 25.10.07 17:58:43, Leo Savernik wrote:
> Am Donnerstag, 25. Oktober 2007 schrieb Andreas Pakulat:
> > > > Um, no. Only if they want to uninstall 4.0, they would have to remove
> > > > all things which depend on 4.0.
> > >
> > > So the plan is to have two kdelibs installed, a 4.0 one and a 4.1 one?
> >
> > There is no plan. Also that would be impossible with the current state
> > of things because both would have files that have the same installed
> > path. So you'd either also need to remove all binaries in kdelibs to
> > someting like foo41 or install kdelibs 4.1 into a separate prefix and
> > not /usr.
> 
> No, it's even worse. Pretended that libkfoo-4.0.0 released under KDE 4.0 is 
> BICed, you have to bump the soname to libkfoo-5, and consequentially release 
> a libkfoo-5.0.0 for KDE 4.1. However, as we have to stay binary compatible 
> for the whole major release series,

Uhm, you're missing the point, which is breaking BC with 4.1, which
means that this:

> we have to *retain* libkfoo-4.0.0 for all binary clients linked
> against libkfoo-4.0.0.

won't happen. Instead 4.1 would ship _only_ with 5.0.0 and anybody who
wants to work with 4.1 would need to rebuild at least and anybody who
needs/wants to stay with 4.0.0 is bound to KDE 4.0.x, which largely is
not further maintained  after the 4.1 release.

Andreas

-- 
You are scrupulously honest, frank, and straightforward.  Therefore you
have few friends.