Bug#53755: [PROPOSED] policy for usage of "xserver" alternative
Will implement current practice, and provide an actual policy for usage of
the "xserver" virtual package which appears in the virtual packages list.
In a nutshell, X servers that interface directly with the display and input
hardware or via another subsystem (e.g., GGI) should provide xserver.
Things like Xvfb, Xnest, and Xprt should not.
G. Branden Robinson | America is at that awkward stage. It's
Debian GNU/Linux | too late to work within the system, but
firstname.lastname@example.org | too early to shoot the bastards.
roger.ecn.purdue.edu/~branden/ | --Claire Wolfe
--- policy.sgml.orig Wed Dec 29 17:01:51 1999
+++ policy.sgml Thu Dec 30 12:58:11 1999
@@ -3140,6 +3140,12 @@
without) of your package.</p>
+ <em>Packages which provide an X server</em> that, directly or
+ indirectly, communicates with real input and display hardware
+ should delcare in their control data that they provide the
+ virtual package <tt>xserver</tt>.
<em>Application defaults</em> files have to be installed in
the directory <tt>/usr/X11R6/lib/X11/app-defaults/</tt>.
They are considered as part of the program code. Thus, they