ANN: split kde ebuilds

menetto · n00b Joined: 05 Aug 2004 Posts: 18 Location: Belgium

I have emerge kde-3.4.0_beta1 with the split ebuilds, but I sometimes find it hard to find the ebuild for the package I want. I want the device protocol, since konqueror doesn't seem to find it, but I can't figure out which package. In kde 3.3.2 it was in kdebase, but now I have emerged kdebase-meta, and still no luck. Anyone has a clue?
I have also a problem with the audiocd protocol. If I try that one, I get the error: There was an error loading audiocd:/ The process of the audiocd protocol unexpectedly terminated (translated from Dutch). I don't know whether this is a bug, or a package I have forgotten to install (which then would have to be in the dependencies). I hope somebody can help. Otherwise I love the splitted ebuilds, just in the beginning it's a little searching to get everything right.

ranmakun · Posted: Sun Jan 23, 2005 5:24 pm Post subject:

corey_s · Apprentice Joined: 29 Jun 2003 Posts: 264

Someone asked earlier about whether the kde-cvs will become made as split-ebuilds -- I'm also very interested in this and it's obvious why doing so would be a good idea... is there any such plans?

firephoto · Posted: Mon Jan 24, 2005 7:33 am Post subject: *edit*

The akregator add feed konqplugin is missing, it should be part of the kdeaddons package but it's lacking a meta ebuild for it. I tried installing the files from a binary I built but the plugin doesn't seem to work for some reason.

*edit

I went ahead and dug into the meta ebuilds to see how easy/hard it would be to make the missing ebuild and it actuall turned out to be rather simple.

I took one of the kdeaddon meta ebuilds, konqueror-uachanger in this case, and changed the references to "uachanger" to "akregator" which was only the ebuild name and this line.

motaboy · Developer Joined: 15 Dec 2003 Posts: 1483

motaboy · Developer Joined: 15 Dec 2003 Posts: 1483

P.S. Please, please, please, report any issue, lacking of some programs/parts at bugs.gentoo.org as it's the right way to deal with bugs. Of course before doing this, just update you portage tree to look if it's already fixed and look if these bugs aren't already reported.
_________________
...

int2str · Guru Joined: 29 Sep 2003 Posts: 361

I have to say I _really_ don't like the split ebuilds so far.

For one, KDE is distributed and maintained in packages (kdebase, kdelibs etc) and not applications. One of the major features attracting me to Gentoo is that the applications are distributed very closely to how the authors distribute it, which makes it very easy to install stuff directly from the authors sites as well as making ebuilds. Heck, most of the time the ebuilds are pretty empty - as it should be IMHO.

KDE's packages will (or should) be consistant in themselfs. The split ebuilds will require much work to maintain consistancy.

For most end users it's much easier to decide which packages they need/want as opposed to which application. And for power users DO_NOT_COMPILE worked just fine in the past, no? If it ain't brok, why fix it?

The added maintenance and portage overhead is not worth the little benefit it brings IMHO.

The good news (for me) is that I _should_ be able to install KDE from the original KDE.org packages instead of using portage. But of course I'll miss a lot of Gentoo "nicenesses" like the .kde directory management.

The split ebuilds are definitely not for me.

Are the package ebuilds (kdebase/kdelibs) still going to be around (and I don't mean as a -meta application ebuild collection) ?

Cheers,
Andre
_________________
Adpot an unanswered post today!

motaboy · Developer Joined: 15 Dec 2003 Posts: 1483

Your problems were already discussed and explained by me and Dan Armak on the gentoo-dev mailing lists and on the splitted ebuilds home page on gentoo.org.

The monolithic ebuilds will rest but we have to look at the power of the splitted implementation (and remember DO_NOT_COMPILE was born for another reason and is totally against on how portage works).

I don't want to speak again about this on this forums or on everywhere other. (so please don't generate a flame)

If you prefer the monolithics ebuilds use them. If you find some bugs or made some fixes report them to bugs.gentoo.org.

Now everyone is free to choose the implementation and you'll be happy to know that one implementation can live with the the others (es. kdebase (monolithic) + kmail (splitted)).
_________________
...

Carlo · Developer Joined: 12 Aug 2002 Posts: 3356

Matteo Azzali · Retired Dev Joined: 23 Sep 2004 Posts: 1133

mario · Posted: Mon Jan 24, 2005 10:03 pm Post subject:

Matteo Azzali · Retired Dev Joined: 23 Sep 2004 Posts: 1133

corey_s · Apprentice Joined: 29 Jun 2003 Posts: 264

motaboy said:

Shan · Guru Joined: 04 Nov 2003 Posts: 556 Location: /dev/null

motaboy · Developer Joined: 15 Dec 2003 Posts: 1483

Loke · Apprentice Joined: 25 May 2002 Posts: 274 Location: Norway

First of all: For as long as I can remember, Ive wanted split KDE packages. However, I always saw this as an issue the KDE people ought to fix, since KDE will only continue to grow. (I still believe this should be fixed by the KDE people) That said, I applaud you trying to "fix" this by splitting the ebuilds.

But, and this is a big but, despite the fact that the implementation is new and probably contains alot of errors and can be improved wastly - I see huge limitations already after trying to set up a slimed down KDE version:

1. In many cases its difficult to know what package to install to get a certain feature. Perhaps you have split things up to much, and some of the ebuilds will be merged in the future. This is certainly going to improve over time.

2. I constantly find reference to various KDE parts, which is not installed, on my desktop. This seems to indicate that the KDE environment is so integrated that it becomes very hard to remove features without breaking something. For example: I dont use or need the kpager, so I dont install it. But I still use desktop preview, and it contains a menu option for kpager - which I of course dont use or dont want. Ive found many such examples of missing parts.

This lead me to the following conclusion after spending a day with the split KDE ebuilds: If you are using KDE as your desktop, you should probably stick with the regular kde packages, either the kde-meta or the parts of kde that you want. If you only want parts of the KDE pleasure for use on other WMs, the split ebuilds are great.

If I were to give you a word of advice, I would focus on splitting the various KDE programs and perhaps leave the libs, config and KDE-under-the-hood-technologies alone. After all, its alot simpler issuing security patches with split KDE packages Great work :-)

_________________
I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself?

Trejkaz · Posted: Tue Jan 25, 2005 1:21 pm Post subject:

Loke · Apprentice Joined: 25 May 2002 Posts: 274 Location: Norway

ercxy · n00b Joined: 26 Apr 2004 Posts: 55 Location: MA

I completely remove kde 3.3.2 and install kde3.4_beta1 by selecting indiviual programs(or program groups).. It is really amazing, This is the best thing happened to my laptop.. I choosen the programs, I usually use and just installed them.. The responsiveness increased enormously(well excitement multiplier might be in charge

results may vary ).
I have complete desktop with progs that I need and want..
basicly i have very clean menu with kdevelop,kmail,kopete,konqueror(+plugins),k3b,kplayer,kile,kuser,kmyfriewall,Ark,knotes
and some modules for kcontrol. This is like a dream.

The level of splitting is; I guess really a matter of taste, but i don't see any problem. since you can do it old way or new way.. more options is better. Your best friends, while installing split kde, are "emerge -s" and "emerge --searchdesc"..
Thanks to everybody who have efforts on this project.. good job!

corey_s · Apprentice Joined: 29 Jun 2003 Posts: 264

I've got a pure kde-3.4-beta split-ebuild system ( i.e., no other versions of kde installed ), yet when I try to install k3b - it keeps insisting on installing arts-1.3.2 and kdebase-3.3.2...

What can I do to install k3b using 3.4-beta dependencies rather than 3.3 deps?

Thanks!

bassvandijk · Posted: Thu Jan 27, 2005 1:35 pm Post subject:

I would like to emerge KDE with USE="-arts". But before I do I would like to know how this will affect my system.

My question is: will applications directly use ALSA or will they use another sound server like gtreamer or something?

GentooBox · Veteran Joined: 22 Jun 2003 Posts: 1168 Location: Denmark

bassvandijk · Posted: Thu Jan 27, 2005 2:51 pm Post subject:

corey_s · Apprentice Joined: 29 Jun 2003 Posts: 264

Dolio · l33t Joined: 17 Jun 2002 Posts: 650