On Wed, 2008-02-06 at 00:28 +0100, Luca Capello wrote: > Hi Ben! > > On Sun, 03 Feb 2008 17:25:49 +0100, Ben Hutchings wrote: > > Luca Capello <[EMAIL PROTECTED]> wrote: > >> since rt2x00-modules-* doesn't depend on the linux-image used to build > >> it, it's not automatically removed with that linux-image. > > > > I agree that it might be desirable for module packages to be removed > > along with the kernel they can be used with. However, if the modules > > are built against an unpackaged kernel, this would then introduce an > > incorrect dependency. > > Well, to build the module you need the linux-headers-$KVER package, so I > fail to see how you can build it against an unpackaged kernel:
You need the corresponding headers, configuration and makefiles. These are usually found through the sym-link /lib/modules/$KVER/build. If you build and install without packaging, "make modules_install" creates a sym-link to the source directory. If you use a packaged kernel, the postinst script of the linux-headers-* package creates the sym-link. module-assistant also allows the directory to be specified explicitly with the -k option. > >> BTW, I don't know anything technical about the module, but shouldn't > >> depend on wireless-tools as well, instead of simply recommending it? > > > > No, you could configure it with network-manager instead. > > Then the question is: can the module be used *without* wireless-tools or > network-manager? There are any number of configuration programs that could be used. Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure.
signature.asc
Description: This is a digitally signed message part
