Re: Splitting isdnutils & co. into non-X and X parts
On Mon, May 08, 2000 at 12:26:44PM +0200, Paul Slootman wrote:
> > > > Just drop the depency on xlib and make it recommend or suggest
> > > > xlib.
> > >
> > > This is not possible - if a user calls one of these
> > > programs, (s)he will get the error message:
> > >
> > > /usr/bin/xyz: error in loading shared libraries: libXyz1:
> > > cannot open shared object file: No such file or directory
> > >
> > > and (s)he will file a bug report!
> > That could be easily avoided by a wrapper script that would explain
> > which packages would need to be installed.
> The problem there is that these are also linked into the menu system,
> and hence any messages generated will silently disappear into
> .xsession-errors or whatever. Also, the overhead for checking whether
> the X stuff is installed or not is silly.
This is funny. If someone has access to window manager menu, he
most obviously has the xlib:s installed.... :-)
Also, remember that only firewall/router sites want to install
isdnutils without X. If someone is building a such system, they
should be clueful enough to realize why something reports missing
X libraries, when they decided delibaretly not to install them.
Atleast if you decide to make atomic packages out of this, make
a isdnutils package that is nothing else but depencies to all what
isdnutils used to be. Everyone hates to notice that functionality
is missing after a upgrade.
Riku Voipio | email@example.com |
Poutamäentie 15 B 78 | +358 50 3313498 --+--
00360 Helsinki | |
Facts do not cease to exist because they are ignored. |