Re: [gentoo-dev] Segregating KDE?

[Dan Armak]

On Saturday 18 September 2004 22:19, Seemant Kulleen wrote:
> The way I see it is that part of the problem with dependency resolution
> is that we're source based.  Debian and the other binary based distros
> have an easier time because for them it (probably) boils down to compile
> once, and then split the binaries, libraries and headers into separate
> binary trees and do the dependency resolution on those.  For example,
> you compile kdelibs, separate out kdelib and khtml and make the latter
> depend on the former, et voila.  With Gentoo this process takes on a
> much much higher complexity.

I'm probably missing your point. How are the dependencies more complex for us? 
KDE apps have very few DEPENDS that aren't also RDEPENDS, so if we had 
separate ebuilds for all the apps, it would be relatively easy to enter all 
the dependencies - it would only require major effort once.

AFAICS the only complex dependency issue arises if you want to separate 
kdelibs into pieces as well, and iirc even debian doesn't go that far; I 
don't think we need to, either.

Come to think of it, there is one other issue; some kde makefiles are badly 
written, and link against libraries built in the source tree under $S rather 
than against installed libraries under /usr/kde/.... To separate the library 
and app into two ebuilds we'd need to fix such makefiles. Because I'm 
speaking from somewhat dated knowledge here, and have nevr actually tried to 
fix such makefiles ;-), I don't know how difficult it'd be or how widespread 
the problem is today.

Anything else I'm forgetting?

-- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951