Bug#337613: [Linux-wlan-ng-devel] Bug#337613: sets WRONG dependency on kernel image for no reason

[Eduard Bloch]

#include <hallo.h>
* Enrico Tassi [Sat, Nov 05 2005, 02:14:57PM]:
> On Sat, Nov 05, 2005 at 11:30:40AM +0100, Eduard Bloch wrote:
> > Package: linux-wlan-ng-source
> > Version: 0.2.2+dfsg-3
> > Severity: grave
> > 
> > Hello,
> > 
> > I have just pointed by a user on your "solution" WRT kernel dependency
> > in debian/control.modules.in and I must admit: IT SUCKS.
> > 
> >  - there is no point in setting a such dependency. People can install
> >    their custom kernels without make-kpkg. RTF Kernel-Howto please.
> >  - constructing "linux-" or "kernel-" is pretty stupid, sorry. You
> >    cannot assume anything, because this applies to debian-kernel
> >    prebuilt versions ONLY.
> > 
> > Please remove this dependency information or move it to Suggests or so.
> 
> Thanks for the polite bugreport!
> 
> Our mistake is that we use the same debian/control.modules.in both
> for modules for standard Debian kernels and for the lwng-source package.
> 
> The former really needs this Depend since these modules are only for
> debian-kernels, while the latter should not for the reasons you
> have highlighted.
> 
> Do you agree? I'll fix this in out tla repository ASAP

I am not sure what I am expected to agree with. Following your
statement, it sounds like you should make that control field in
control.modules.in be some custom substvars variable, and then detect
your build environment in debian/rules and pass that variable part via
dh_gencontrol options _only_ in that special build environment.

Eduard.

-- 
So, your "solution" is to ask "Should I break your system now or after
the next reboot?". Debconf is not an alternative to fixing the
problem. Such questions are still unacceptable bugs.
              -- asuffield in debian-devel about crazy linux-2.4 repackaging