[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Maintaining kernel source in sarge

On Mon, May 19, 2003 at 10:02:58AM +0200, Ola Lundqvist wrote:

> I'll start here:
> Kernel package policy:
  "kernel image" to avoid confusion between kernel source, kernel headers,
kernel modules, etc.
> ----------------------
> * It should only exist one kernel-source package.
> * Every modification to the kernel should be added as a patch package.
> * Modifications may be separated to make it easier to administrate and
>   for other people/packages to use it.

Kernel image packages must include a list of patches which have been
applied, and the packages from which they came.

> 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.
> * 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.

It would be a significant gain if kernel modules could always be built
against kernel-headers, without requiring full kernel-source.  Is there any
situation where this is not feasible, or could it be made a requirement?

 - mdz

Reply to: