xvfb and xnest aren't used terribly often, so I think they should be separate from USE="minimal" since minimal turns off very commonly used things like DRI. There was some discussion on IRC about the virtualx eclass needing xnest. Seemed to me like we should just bite the bullet and made xnest a USE flag and clean up afterwards.
Created attachment 264639 [details, diff] patch to add xnest and xvfb USE flags
*** Bug 352637 has been marked as a duplicate of this bug. ***
We have virtualx.eclass patch quite handy in x11 overlay. I should really merge it tomorow... Also for the useflags we once agreed that minimal should control most server stuffz. Maybe we could rethink our strategy here... @remi: what is your opinion?
(In reply to comment #3) > Also for the useflags we once agreed that minimal should control most server > stuffz. > Maybe we could rethink our strategy here... I need xvfb for xpra, see bug 352974. I am currently using an ebuild similar to the patch uploaded on 2011-03-04 by Matt Turner. Having USE="xvfb minimal" saves me installing several packages. This is on a headless box that will never need display drivers of its own. I can't remember how many packages, but it's a significant little handful. I believe this patch is the most "correct" way to handle xvfb (I don't know about xnest)
Finally committed. xnest and xvfb are now in the list of IUSE_SERVERS and have been removed from the minimal USE flag's control. I also modified the virtualx.eclass to depend on xorg-server[xvfb] instead of xorg-server[-minimal]. Let me know if I broke anything (I sure hope not)
