Created attachment 274665 [details] Improved ebuild for kdebase-runtime-meta Some components are not really important to run single kde programs as far as I see it. Not everyone wants kwallet or knetattach (much less in Gentoo where people tend to configure networks system-wide, specially in non portable machines). How about letting the user choose via USE flags?
I'm sorry but no, we already decided in a previous meeting to avoid such splitting.
(In reply to comment #1) > I'm sorry but no, we already decided in a previous meeting to avoid such > splitting. I am not going to fight about this. I'll just overlay this, and while I am at it I'll also add a way to disable activities, I am sure I am not the only one who find them useless. This will mean: 1) two less useless daemons eating ram 2) one less useless popup when opening chromium (kwallet acting up) Only advantages for me ;) But, in any case, is there any info about this meeting(s) that I can read just for the sake of curiosity?
I'll provide more info tomorrow (too busy now, sorry). In short, we had long discussions about kdebase-runtime in the past, because we were hitting very weird bug reports that were not so easy to debug (and it was getting more complex when those reports were going upstream directly). That's why there is an ewarn now when this package is not installed.
(In reply to comment #3) > I'll provide more info tomorrow (too busy now, sorry). In short, we had long > discussions about kdebase-runtime in the past, because we were hitting very > weird bug reports that were not so easy to debug (and it was getting more > complex when those reports were going upstream directly). That's why there is > an ewarn now when this package is not installed. Thank you. KDE is big and I can see how removing these pieces could create problems in some application though in my case it doesn't. Still, I wish the whole K thing was more modular but that's a thing for upstream. Thanks for the input.
