severity 362253 important thanks On Friday 14 April 2006 06:52, Russ Allbery wrote: > Well, I run discover on all my systems as a matter of course, so I > suppose I'm not the most sympathetic of audiences. I've not had those > problems with it.
That is not an argument. > > If it were a dependency of a meta-package, at least you could remove > > it and only lose the meta-package. But xserver-xorg *depends* on it > > now, rather than just recommending it, so you're stuck with it. > > ...it sounds like your primary objection is to the boottime behavior, > not to the use for X configuration. I do still see the case for > changing from Depends to Recommends provided that the X configuration > sequence supports it, but for your main complaint, can't you just > disable the init script? Disabling init scripts is not something we should require of users. The proper way to deal with this is to _at most_ make it a recommends instead of depends. If the configuration scripts cannot currently handle a missing discover currently (which I doubt), then they should be fixed to fall back to manual configuration if discover is not present. The best solution of all would be to no longer use discover at all: the discovery of graphics cards has always been a by-product of discover rather than its main function. Its main function is hardware discovery and automatic kernel module loading with 2.4 and older 2.6 kernels. This function is obsoleted with recent 2.6 kernels for which udev is the preferred method. In Debian Installer the only reason we still install discover (discover1 even) is because it is needed for X configuration, but we'd rather drop discover altogether for 2.6 based installations. Note that this was more or less confirmed on debian-x earlier [1] although it was indicated that this does not have high priority. I very much hope a replacement will be realized in time for Etch though. In the mean time, recommending discover is acceptable, depending on it is not. Additional note. Depending on tools used for hardware discovery may not even be sufficient. If the tools are used in the preinst script, there is no guarantee that the tools will be unpacked at the time the X preinst script runs. Even if the tools are only used in postinst there is no guarantee they will be configured and thus in a usable state. This is why currently the installer installs mdetect and read-edid _before_ tasksel is run. Finally note that xfree in Sarge only suggests the discovery tools. $ apt-cache depends xserver-xfree86 xserver-xfree86 Suggests: discover Suggests: mdetect Suggests: read-edid [1] http://lists.debian.org/debian-x/2006/04/msg00046.html
pgpxh8UpPQPhI.pgp
Description: PGP signature
