Server install with beta2 installs XFree86-FBdev even though X wasn't
selected. Additionally, Printer Support brought in XFree86-libs and xfs.
IMO, these don't make sense to have installed on a server install unless
Agreed. IMHO a server install should not contain any X11 cruft at all.
Matt would you please verify that a Server class install w/o the X Windows
component selected in the component selection screen does not pull in any X
packages which are avoidable?
ghostscript needs libX11.
don't know why fbdev would be pulled in.
Ghostscript needs xfs as well for mkfontdir I believe.
Perhaps we should make mkfontdir a separate subpackage of XFree86?
I've no idea about XFree86-FBdev though. The only thing that uses it is
the installer I believe. It should be destroyed after our final release.
While I agree that a server install shouldn't contain any X11 cruft, this
requires taking mkfontdir out of the xfs package just for ghostscript. Also,
xfs is a SERVER, a font server in particular, and it does have a use on a
server if someone wants to network serve fonts. XFree86 need not be
installed for xfs to work.
As for anything requiring the X libs package on a server, many applications
that are normally ran from the commandline can autodetect they are running
in X and enable special X features. In order for dependancies to be met for
these apps, X-libs and perhaps other stuff need to be installed.
this is fixed in qa0319.2 ... as a side effect, minimal installs now fit on only
one cd ...