On Mon, 24 May 1999, Branden Robinson wrote:
<p>
Such programs should be configured <em>with</em> X support,
- and should declare a dependency on <tt>xlib6g</tt> (for the
- X11R6 libraries). Users who wish to use the program can
- install just the relatively small <tt>xlib6g</tt> package,
- and do not need to install the whole of X.</p>
+ and should declare a dependency on <tt>xlib6g</tt> (which
+ contains X shared libraries). Users who wish to use the
+ program can install just the relatively small
+ <tt>xfree86-common</tt> and <tt>xlib6g</tt> packages, and do
+ not need to install the whole of X.</p>
I still fail to see why do I need xfree86-common to execute emacs or
ghostview in console mode (as I always was able to do under Debian 2.0).
When I asked about xlib6g's new dependency on xfree86-common, people said
"this is to avoid a lot of packages to depend on xfree86-common". Well,
hiding real dependencies via indirect dependencies is not the way things
are usually done in Debian.
Which exactly is the problem which is intended to be solved by adding this
dependency?
Thanks.
--
"89e9dec9fdd0691f4fc9026d7b6eb892" (a truly random sig)
