Re: Kernel module package depending on kernel-headers.
On Fri, Sep 13, 2002 at 12:23:31PM -0400, David Z Maze wrote:
> Sven LUTHER <email@example.com> writes:
> > I am packaging unicorn :
> > unicorn - Kernel modules for the Bewan ADSL PCI st modem
> > The upstream source come with a make file enabling to build it from only
> > the kernel-headers, without there really being a need for the
> > kernel-sources (in particular, it is a standalone tarball, not a patch
> > to be used with kernel-package, and as thus, i don't use the dh_make
> > kernel module option, but am doing a single binary package).
> > Ok, now to my actual question :
> > I have to build depend on kernel-headers, and the resulting binary does
> > depend on the corresponding kernel-image.
> > How do other module packages handle this, do someone know at a good such
> > package i could use as example ?
> The standard way to do this seems to be to have your module source
> package's 'debian/rules binary' target build a tarball of itself in
> debian/tmp/usr/src, such that installing the package creates
> /usr/src/unicorn.tar.gz. Unpacking that will create modules/unicorn,
> which should be a well-formed Debian source package, and running
> 'debian/rules kdist-image' there will go off and build the module.
It all sounds a bit complicated ...
> /usr/share/doc/kernel-package/README.modules describes the
> kernel-package interface to module building; the user will need to run
> 'make-kpkg modules-image' after having unpacked
> /usr/src/unicorn.tar.gz and building their kernel. My understanding
> is that the kernel-headers packages are mostly useless, since they
> don't include details specific to the kernel build that you need to
> build modules.
Well, but the modules in question builds well with the kernel-header
(they just need some of the .h it seems).
> <plug>i2c is a simple source package that uses the "tar yourself up
> and go" scheme; lm-sensors also has a user-space component. I don't
> necessarily claim that either is "good", but they both work for common
> cases using kernel-package.</plug>
> (linux-wlan-ng uses a different packaging scheme: the user needs to
> manually run 'apt-get source' in /usr/src/modules. This isn't
> necessarily bad, just different.)
Mmm, i will think about it.