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

Kernel image and OOT auto builder environment (Was: Using out of tree modules in d-i)?

On May 22, 2013, at 3:52 PM, Ben Hutchings wrote:

> Quoting from the report of our 2009 meeting,
> <20091015123106.GA16736@kyllikki.org>:
>> out of tree modules
>> -------------------
>> After a somewhat involved discussion taking into account the FTP
>> masters extreme irritation about trying to match binaries to source by
>> hand for the lenny release it was resolved to remove
>> linux-modules-extra and -nonfree as they are an impossible to support
>> approach.
> The Built-Using header should cover FTP masters' concerns.  However it
> is still the case that omnibus source packages are unsustainable as many
> OOT modules are not kept up to date with the kernel API.

I haven't been keeping up with the inner workings of Debian GNU/Linux
the last couple of years, so please take this as-is.

Is it possible to setup an automatic build system for kernel and modules?

I know that we have (had?) an auto builder to build everything automatically
(think it was mostly (?) used for the ports), but I was thinking about a
special build system here. Very possibly just a modification of what we
already have...

That is, a special place to upload the kernel source to, and once the auto
builder have successfully built a linux-image* package(s), then it will
look in a special list for source packages to build as well. And once
all those have succeeded to, THEN it will upload the kernel (and the
OOT modules) to the ftp archive...

To clarify: the kernel maintainer does not build and upload the package
to the archives, but only uploads the source package to this special
build system and it will do the rest...

That way OOT modules should be able to keep up with the kernel releases
and uploads without much (hopefully) extra work. And the added benefit
is that once a new kernel version is available in the archives, the
OOT modules will as well, without any extra lagg...

This should be reasonably easy to do, and I volunteer to do the initial
setup and/or prof-of-consept for all the versions we currently support
(oldstable, stable and unstable).

Reply to: