KJSEmbed removal part 2

Leo Savernik l.savernik at aon.at
Wed Jul 25 18:11:46 BST 2007


Am Mittwoch, 25. Juli 2007 schrieb Thiago Macieira:
> Dirk Mueller wrote:
> >On Wednesday, 25. July 2007, Thiago Macieira wrote:
> >> If the library's headers is not installed and there's no .la file
> >> mentioning kjsembed, it won't be a problem to remove it later.
> >
> >thats wrong on platforms that don't use -Wl,-unneeded. the libs linking
> >against libkio will still have a libkdeui NEEDED entry and then fail to
> > start up when libkdeui is gone.
>
> You mean --as-needed?
>
> Well, that only happens for kdelibs libraries, because it's the same CMake
> project.
>
> For modules other than kdelibs, as long as kjsembed is mentioned nowhere,
> nothing else will link to it.
>
> But, if possible, don't link to kjsembed in libraries. Only in final stuff
> (modules, applications).

That still doesn't explain why you think it isn't BIC. Say, in module kdebar 
there's an app KFoo shipped with KDE 4.0 linking against kjsembed.

If you upgrade kdelibs *only* to 4.1, by definition of BC, all installed apps 
for KDE 4.0 must run unaltered. However, as kjsembed vanishes with the 
upgrade, KFoo linking against kjsembed stops working.

So why is removing a library BC just because it isn't referenced in 
a .la-file?

mfg
	Leo





More information about the kde-core-devel mailing list