Re: Custom kernel build - best way to generate a package

[Henning Schild <henning.schild@siemens.com>]

Am Thu, 25 Jan 2018 09:50:14 +0100
schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:

> Hi all,
> 
> as indicated before, I'm looking into providing a framework for isar
> to help users with building their own kernel packages from
> un-debianized kernel sources. I'm now scratching my head how to do
> that best. Options I'Ve found so far:
> 
> 1. make bindeb-pkg (from upstream kernel)
> 
>    Downside: currently requires patches to feed in missing runtime
>    dependencies of the generated package. Also, it seems this is not
>    designed to create full replacements of the standard debian kernel
>    packages. Might be an uphill battle on the long run.

We do have an internal recipe to build a kernel like that. Ben
suggested that as a viable approach. I later found that such a kernel
has a pretty broken control-file and suggested an upstream patch.
https://lkml.org/lkml/2017/11/27/659

> 2. Provide debian/ folder in isar so that dpkg_runbuild works
> 
>    Question is here where to pick up the debian/ folder from. The
>    original debian kernel package? The version that Frank once create
> as demo [1] (BTW, how was it created?)?

Maybe Ben can enlighten us, i guess the folder is maintained for a
specific kernel and can not be fetched from somewhere to match a wide
range of versions.
 
> 3. make-kpkg
> 
>    Still unclear to me what pros and cons are here.

I think that one is dying and we would have to have a close look at the
control-information, probably also broken. Last thing i remember from
another project is, that it produced broken header-packages.

Maybe there is a 4. and 5. that we are not aware of? Ben?

Henning

> Any comments / suggestions would be highly appreciated!
> 
> Thanks,
> Jan
> 
> [1]
> https://github.com/ilbers/linux/commit/b7ab449238b8e59943849a10c95d578aa01d70e7
>