Re: Maintaining kernel source in sarge

[David Z Maze <dmaze@debian.org>]

Ola Lundqvist <opal@debian.org> writes:

> Kernel module policy:
> ---------------------
>
> * Kernel modules must be provided as a "binary source" package.
> * Module source packages should provide a debian/rules file.
> * The debian/rules file must compile the module if KSRC=kernelsourcedir
>   and KVERS=versionname is priovided.

I'd be slightly happier if the targets kernel-package used were
supported here, 'debian/rules kdist-image' and such.  (This is to
accomodate "binary source" packages that have a single debian/rules
file that's copied verbatim from the source package to the binary
package; both lm-sensors and i2c work this way, don't know about other
packages.)

> * The debian/rules file may fail if an unsupported version of the kernel is
>   provided by the environment.
> * The debian/rules file may fail if no kernel-headers is in that location.
> * The debian/rules file should handke KMAINT and KEMAIL env variables.

...in fact, this looks a lot like what kernel-package currently
documents.  Is a separate policy from the kernel-package documentation
needed?

(FWIW, i2c and lm-sensors both successfully build against only the
kernel headers, via the kernel-build-* packages.)

-- 
David Maze         dmaze@debian.org      http://people.debian.org/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell