On Wed, 1 Feb 2012 14:54:23 -0600 "Timothy Pearson" kb9vqf@pearsoncomputing.net wrote:
Am 01.02.2012 20:47, schrieb Robert Xu:
All there: https://gist.github.com/1718892
Feel free to speak up should you have an opinion - the door is always open!
Before misinformation about KWin spread, I dare to speak up.
17:47:35 <kb9vqf-offsite> Personally I would hate to have to install kwin, which relies on a bunch of other KDE4 libraries and
automatically
installs that akodani garbage scanner stuff, just to use TDE
Personally I hate statements without checking facts. KWin neither requires Akonadi nor Nepomuk. My CI-system has neither one installed. But to give proof:
martin@martin-thinkpad:~$ aptitude show kde-window-manager | grep akonadi martin@martin-thinkpad:~$ aptitude show kdebase-runtime | grep akonadi martin@martin-thinkpad:~$ aptitude show kdebase-workspace-bin | grep akonadi martin@martin-thinkpad:~$
So this should not at all be a problem for Trinity - yeah \o/ :-)
As I said... "unless I am wrong" :-) I was speaking from past experience only, and the basic steps outlined still hold. twin is not going to go away, but kwin should be allowed (along with any other WM) in TDE sessions.
I meant nepomuk, not akodanai. It can be hard to keep all of the (foreign language) codenames straight in one's mind. :-)
On my Ubuntu system nepomuk has to be installed with kwin:
[...]
so that is NOT an option for me.
Gentoo doesn't appear to require nepomuk as a kwin dependency (~30 other packages I don't have installed, yes, but not nepomuk), so I suspect you're running into either an Ubuntu quirk or something to do with semantic desktops, which are not an absolute requirement for KDE4 IIRC.
The main problem I'm seeing is kdelibs, which *is* a kwin dependency as far as I can tell, and which wants to drag in strigi and a bunch of other unwanted-by-me cruft ranging from phonon to consolekit. Either all references to kdelibs that can't be replaced with tdelibs would need to be scrubbed from the kwin code, or a small kdelibs-subset containing only the functions vital to kwin would need to be created. Without knowing the code, I can't say whether that's possible or not--presumably, Martin can tell us.
If we're going to include kwin in Trinity, we have to cut it down those of its dependencies that aren't used by anything else to at most 2-3 smallish packages, regardless of what those packages are, IMNSHO. Concentrating on akonadi/strigi/nepomuk is a red herring.
Sounds reasonable. Martin, can this be done?
Tim