kile 1.6.3 has been running on my system for quite a while now. Since yesterday it requires kdegraphics. It builds fine without it and it also runs fine without it. kdegraphics would need kdebase... As I said until now I was fine without these two packages and the kile version did not change. I tried rebuilding kile again without these two "deps" and it is just fine.. It would be great if this "dependency" could get removed from the kile ebuild again.. Reproducible: Always Steps to Reproduce: 1. emerge -Duaqv world Actual Results: kile requires the kdegraphics package which it does not seem to actually need Expected Results: not require it... I am running kile but using xfce as desktop environment, therefore dont have kdebase.Since it is not a small package I'd rather not compile it...
see Bug 62239 :| I'm not fine with a lot of Gnome stuff, but have no chance to avoid it, because the Gnomes want to give their users the best experience - and blindly running into an use flag/option hell is no solution. Imho kdelibs+kdebase has to be acceptable. If you don't like it, you can still put a modified ebuild in your local overlay. That's what I am forced to do with some Gnome stuff, too.
kdebase is huge... at least considering the fact that I would only need it for kile... Couldn't you just make a warning to use external viewers without kdebase? or a useflag internal-viwer or something like that so both of us are happy again? :) right now I have a modified ebuild but this is not really a solution to the problem itself...
How about removing the kdegraphics dep from kile, and having it spit out a message in src_unpack() or something that warns you if you don't have kdegraphics installed that it's advised to install it?
Caleb, I don't think that postinstall information for optional (even runtime) dependencies is desirable, since it defeats the idea of getting a clean (semi-)autmatic install. In the best of all worlds, there would be no extra information needed to be read. On the other hand I don't like the way we run into an use flag hell. The mplayer and the php sapi ebuilds are examples, where it really begins to suck. Even the floating ideas (flag defaults inside the ebuid, use flags sets) will only ease the problem a bit, but not decrease the complexity of all the possibilities to combine all the packages and their different options. Gentoo may come to the point, where less options are the better way to go. Back on topic: As noted above I'm not a fan of additional use flags, but if it is really needed to make kdegraphics optional, a use flag is the only tool we have. We use the kde flag in the k3b ebuild already, to make the kde-base dependency optional. Im not sure, if it was the original meaning of this flag, to add additional kde-base/* dependencies to stuff that depends on kdelibs already, but using it would be the compromise to prevent adding another use flag. The description of the flag "kde - Adds support for kde-base/kde (K Desktop Enviroment)" doesn't really fit to this usage and should be accomodated, then. What do you think?
Yeah, I think making it depend on the kde use flag would be just fine. It's fairly clean, and it's easy to edit out that functionality with /etc/portage/package.mask if desired.
done, flag description is fine for you as it is?
