Because it is simply wrong. You don't need to have a X server installed on your system, think of remote X. The dependency comes from the virtualx eclass and only seems to be needed to run 'make check'. Maybe better just don't run make check when there is no X server available? But forcing to install xorg-server (and its dependencies) just to run "make check" is a bit annoying. You can workaround that by disabling the 'X' useflag for gtk+, but thats rather unintuitive.(The X useflag imho doesn't really make sense anyways for something like gtk+ ;) ) note: this behaviour is new in 2.8.19, it was fine in 2.8.12.
the X flag sense is the same as for other packages. It activates X11 related functionnality. Did you know that qt3 can be compiled without X support. I guess this is the same thing here hence the USE flag.
> You can workaround that by disabling the 'X' useflag for gtk+ You are joking, right? # euse -i X global use flags (searching: X) ************************************************************ [+ D ] X - Adds support for X11
(In reply to comment #1) > the X flag sense is the same as for other packages. It activates X11 related > functionnality. Did you know that qt3 can be compiled without X support. I > guess this is the same thing here hence the USE flag. As i said, the X useflag is _only_ used in virtualx eclass. It changes _nothing_ in the way gtk is compiled. gtk never had a X flag until quite recently, it was only added to: -- fix the make check stage which wants to run a gtk+ app (so run it in a virtual X display). -- (according to the cvs log) (In reply to comment #2) > You are joking, right? no, I would tell you something funny if I want to make a joke. > # euse -i X > global use flags (searching: X) > ************************************************************ > [+ D ] X - Adds support for X11 > hmm? What that's supposed to tell me?
Yeah, USE="X" enables support for X server, everywhere, for every ebuild that has this flag. Surprise surprise! :P
Closing this, if you don't want X, don't stick X use flag into make.conf - very simple and obvious.
(In reply to comment #4) > Yeah, USE="X" enables support for X server, everywhere, for every ebuild that > has this flag. Surprise surprise! :P kinda funny that I have several apps installed with USE="X" with no X server installed :P USE="X" enables support for using X11 for drawing, i.e. using and linking against libX11 and friends. But the X11 protocol works also with X clients and X server on a different system. You don't have to have the X server installed in a system to run a X application. Ask google if you don't believe me: http://www.faqs.org/docs/Linux-mini/Remote-X-Apps.html If that is not enough just look into your portage tree. Every dependency based on the X useflag(that I have seen so far) _only_ pulls in the neccessary _X libraries_ (libX11/libXrender/.../etc). But _NOT_ the server. The only "bad guy" here is virtualx.eclass. If you on the other hand look which ebuilds actually depend on xorg-server there are only: a) X drivers and xorg-x11 meta ebuild -> fine b) x11-misc/xoo - wrapper around Xnest, fine too c) dev-perl/PGPLOT, media-video/avidemux, media-video/kaffeine << no idea about those, but probably wrong as well *scnr* thats all. If that still doesn't convince you, emerge gtk+ with USE="-X". You will see it still uses X, is linked against libX11 et all. huh? surprise? kinda doesn't make sense to me :p And if you still don't see my problem, I will just shut up and walk away because obviously I'm completely unable to explain a simple problem to you( maybe I can take lessons somewhere *scnr*).
So, disable the flag like everyone else? There's no bug whatsover here, you can get rid of the xorg-server dependency just fine by setting appropriate use flags, that's why they are there. If you set USE="X", you get X. Not a bug. > If that still doesn't convince you, emerge gtk+ with USE="-X". > You will see it still uses X, is linked against libX11 et all. huh? surprise? > kinda doesn't make sense to me :p Maybe you go file a couple of Debian bugs as well? http://packages.debian.org/stable/source/gtk+2.0 Or, maybe you just read up the source and go check what it actually needs to compile, instead of filing bugs that are not bugs? Much appreciated. Thanks.
