Re: [gentoo-dev] Segregating KDE?

[Simone Gotti]

On Sunday 19 September 2004 16:48, Dan Armak wrote:
> > The aren't badly written, this is the right behavior, For example kmail
> > wants to compile against libkdepim. You can't link against a library that
> > isn't already installed o an old installed one with less functions.
>
> Should be a fallback IMHO. configure can check for things like that. At
> least, we're going to have to make it do that if we go through with this
> :-)
> As for old versions, isn't that what library versions are for?
You're right. The real problem is that library version usually are the same in 
ALL kde 3.X. Because they must be Binary Compatible (B.C.) (this means of 
course al source compatible). In c++ you can mantain the B.C. also adding 
some new methods to a class, with the exception that this one doesn't have to 
be a virtual method. I've noticed that between every version of kde some libs 
ends with the same *.so.X.X also if they adds some new functions (I hope to 
be wrong...).


By the way, I think that it's possible to split EVERY kde program/libs in a 
single package, this can be possibile by heavily patching the Makefiles like 
you've said so they can link to an installed lib instead of the local one, 
this libs will be a dep of the program and it should be of course a different 
ebuild. 

I'm already giving a little help to caleb and carlo on the kde ebuilds and if 
ypu and they think that a lot of people thinks that having single kde 
programs instead of the standard modules will be a better idea I'll be VERY 
happy to start hacking on this. My great fear is that it will slow down the 
development of the ebuilds because this bring to a lot of additional work! 
Think that probably the Makefile's patches must be changed on every kde major 
release.
 
All I need is to know if you (gentoo kde developers) are really interested on 
this work. Let me know!

Bye!
-- 
Simone Gotti
<simone.gotti@×××××.it>
http://kde-bluetooth.sf.net

--
gentoo-dev@g.o mailing list