[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: xlib6g now depends on xfree86-common (?)

On Tue, 9 Feb 1999, Branden Robinson wrote:

> I wanted a place to centrally manage the mess of symbolic links regarding
> an X installation that are mandated by existing practice and the FHS.
> I want only one package to "own" the symlinks /usr/bin/X11, /usr/lib/X11,
> etc.
> People with X server-only installations have no need for the xlib6g
> package.
> Other types of X installation will have xlib6g, xserver-common, or both.
> So it makes sense that anything they both need should go in a separate
> package.  Thus xfree86-common.

This does not answer the question "why xlib6g as such needs it?".

Please, tell me something that breaks when you have xlib6g installed and
not xfree86-common.

 "1a25b65fa8bf1a0bcb470a6de79f97d7" (a truly random sig)

Reply to: