BIC in libkonq
apaku at gmx.de
Wed Aug 4 12:34:56 CEST 2010
On 04.08.10 11:16:01, Modestas Vainius wrote:
> On antradienis 03 Rugpjūtis 2010 22:52:36 Dirk Mueller wrote:
> > libkonq is
> > an edge case, it is used in quite some other modules, on the other side,
> > due to the anything that depends on *workspace* must require the exact
> > version anyway, making an exception for libkonq doesn't make that much
> > sense to me.
> Yes, probably most of libraries are local to kdebase-workspace. But if they
> are local, they should not install headers to the world. But they all do
> (why?). A few libraries in kdebase-workspace are definitely public, for
> example libsolidcontrol (afaik, it broke BC in 4.5 without bumping soname) and
> libtaskmanager  (it broke ABI in 4.4 in comparison with 4.3).
The libs from ksysguard (libprocess and libprocessui) are also used outside
> The recent example on top of all that workspace stuff: libsolidinterfaces was
> moved to kdelibs 4.4 with completely reworked API and without any soname bump.
> Looks like KDE violates soname concept for the sake of what? Because a single
> change in CMakeLists.txt is too hard? Or SOVERSION 4 is such a good looking
> number that there is a strict policy not to touch it? I'm sorry but I don't
> know how else I could explain this.
You overestimate how many people actually have a clue about sonames. Most
developers do not know what that number means or when it should be
increased. They simply use the variable set by FindKDE4Internal and are
done with it.
> Anyway, at this point I see this as completely lost battle. I guess we will
> need to start adding distro patches (sad) for bumping sonames of those public
> libraries because you do not seem to have much interest in following well
> defined practises in the unix world which are supported by
As Lubos said, you're barking up the wrong tree, the release team can do 0
about this. The developers actually can, but most of them don't read this
You are a very redundant person, that's what kind of person you are.
More information about the release-team