A. R. schreef: > On 5/13/05, Allan Spagnol Comar <[EMAIL PROTECTED]> wrote: > >>Hi All, I am having a little doubt about qt and kde user flags, I am >>using Gnome in my system but I like some kde programs, so I have gtk >>and gnome flag, should I use kde and qt flags to or should I put the >>-kde and -qt ? >> >>-- > Hi, > > It is my understanding that even if you disable those flags > (-kde -qt) and you try to emerge a package that depends > on kde and qt libraries, those will be compiled as well. > > As an example, I am running xfce4 (gtk2) and my use flags have > -kde -qt, if I try to emerge k3b, it shows that it wants to emerge: > (just a snippet) > > x11-libs/qt > kde-base/kde-env > kde-base/kde-libs > > The flags only affect what a given package is *able* to support. > > In this example, if I want to be able to use k3b, some > kde and qt libraries need to be compiled so it can run, > and that is completely different than the software > supported by k3b that can be customized through altering > the use flags. > > HTH, > > -AR >
This is true, but not exactly clear. Continuing with the K3b example (because it's a good one for this purpose), I have often compiled K3b without the -kde and -arts USE flags, because by preference I use GNOME or Openbox or IceWM, not KDE. Because K3b relies on kdelibs and qt before it can be compiled at all, those will be compiled when I emerge K3b, no matter what my USE flags say. They are required dependencies. However K3bsetup2 is an optional dependency. It is required if you want to integrate K3b into KDE (+kde), and sound output (the "rasberry" sound when a burn fails, the fanfare when it succeeds, etc) is an optional dependency that will be compiled with the +arts flag, also for integration with KDE. So if I am running K3b under GNOME, and thus have emerged it -kde and -arts, I won't have K3bsetup2 or the sound business, but then again, I'm running it under GNOME, so I don't actually care that much (I can do the setup manually if I must, and it's not worth it to have aRTs just to hear a fanfare when my burn succeeds). That's what an optional dependency is. If I don't have KDE installed, though, and try to emerge K3b +kde and +arts, K3b will not only emerge the required kdelibs, but also kdebase, because k3bsetup2 (the optional dependency added by +kde) requires that as well. So basically I'll get KDE, because I requested that K3b be integrated with KDE-- and that obviously requires that a viable KDE installation be present, so it will be created if it does not exist beforehand. So if you want your programs to have all possible integration into the KDE environment (perhaps you want to give it a spin, even I think that 3.4.0 is pretty nice), then use +kde and +arts. +qt you probably want if you want to use QT based programs (some of which are not related to KDE, for instance DVD:Rip, iirc, and probably Quanta). But if you know that you just want some KDE based programs, but not KDE itself, you can try using -kde and -arts (it should always be -both, because aRTs pulls in KDE if present). However, you should be aware that there are not all that many KDE-based programs that don't require KDE to be present to run, but only the libs. That may have changed with the split ebuilds, but up to now the only ones I know of are K3b and Krusader (mostly because they're the only ones I use when not using KDE). It's not like you can so much install Konqueror without KDE, for example. But again, that may have changed. Hope this helps. Holly -- gentoo-user@gentoo.org mailing list
