Bug#380402: madwifi-source: Unneeded dependancy in generated madwifi-modules-[kernelversion] package

[Loïc Minier]

On Sun, Jul 30, 2006, infernix wrote:
> My point here is that if modules are built for a custom installed kernel 
> (so no make-kpkg one), it should either be general for all module source 
> packages to depend on [linux|kernel]-image-[kernelversion] or recommend 
> it. What I'm seeing here is that for fgrlrx it's recommended, and for 
> madwifi it's dependant on it.

 Do I understand correctly that you try to make-kpkg the modules and not
 the kernel?  This seems broken to me.

 You may or may not use Debian kernels, you can use make-kpkg against
 the upstream or Debian sources for the kernel, you can build manually
 the upstream or Debian sources of the kernel.
   There are no madwifi binary modules, but you can make-kpkg against
 the Debian sources for the modules, you can use module-assistant
 against the Debian sources, you can build manually the upstream or
 Debian sources.

 What you can not do is combine a custom kernel with make-kpkg-ed
 modules or module-assistant-build modules.  This seems a very minor
 constraint to me and even makes sense -- even if we could technically
 imagine detecting whether this is a make-kpkg-ed kernel or a
 manually-built kernel and generate or not a dependency.

-- 
Loïc Minier <lool at dooz.org>