Fernando Serboncini posted <[EMAIL PROTECTED]>, excerpted below, on Mon, 07 Feb 2005 12:07:26 -0200:
> I don't think I see the light here. > What's the use of virtualx.eclass without X support? It basically uses > xhost and Xvfb to create another DISPLAY, so I don't think it even runs > without virtual/x11 installed. I could be wrong here, but I believe the parent was referencing the fact that portage doesn't do conditional eclass inherits yet (according to a comment I saw posted not long ago). Thus, what Patrick is attempting is to allow an ebuild some method to inherit virtualx.eclass for use when X is in USE, so it can be used then, without a mandatory depend on virtual/x11 when -X is in use. Since portage doesn't have such conditional handling built-in, currently certain ebuilds that don't need X unless it's in USE, don't depend on X, even tho they inherit this eclass. That breaks them when X IS in use but not yet installed (as I read things), because the dependency tree is incomplete. However, to fix the ebuilds directly would cause them to depend on X even if they aren't going to use it based on USE=-X, so he's trying to punt and let the ebuild be inherited but gracefully do nothing if USE=-X. That is of course how I'm reading things. Does that scrap enough mud off the window to let some light thru, or just spatter more on it? <g> -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
