Re: Bug#63368: libglide2-v3: Unsatisified Dependancy
>>>>> "Manoj" == Manoj Srivastava <srivasta@debian.org> writes:
Joseph> device3dfx-source builds device3dfx-module. Since you
Joseph> NEED THAT MODULE in order to use Glide for the Voodoo3,
Joseph> the dependency BELONGS THERE. It is not my problem that
Joseph> the maintainer of that package chooses not to build the
Joseph> module for standard kernels.
As a system administrator, I am not sure I like the idea of
one package depending on kernel modules in this way.
I would prefer, no dependencies, but a big warning saying that the
module must be installed before it can be used. That way, if I really
want the module, I can compile it myself, but if I don't (eg perhaps
it is incompatible for some reason with my computer), then I won't
have any unexpected surprises.
This is what other packages do, eg looking throughout my available file:
--- cut ---
For diald to work the kernel *must* have SLIP devices, either compiled in
or as a module, even if only PPP connections are made. In the latter case
you should also have pppd, of course.
--- cut ---
--- cut ---
This package does not contain module binaries. You must build the
iBCS module your kernel needs.
--- cut ---
--- cut --
You WILL need ip accounting in your kernel and at least two ip
firewall rules. This version allows you to specify which
accounting rule to watch for tx and rx and you will have to
enter them in ipfwadm or use the debian package ipac.
--- cut ---
I do not think it is possible to have dependencies on kernel modules,
unlike standard modules, simply because to many different
configurations may exist, and it is not possible to tell what may be
required by an individual computer/administrator with a static check.
However, I would be surprised if no one disagrees with my opinion ;-)
(sidenote: perhaps the messages quoted above should have something
like "this option is not compiled into the default Linux kernel
supplied with Debian. Please see http://.../ for details." The URL
could give information on how to compile the kernel and/or the
required module. I suggest a http address, and not a local file, and
it is highly probably it will need to be updated as new users find
more problems).
--
Brian May <bam@debian.org>
Reply to: