Re: [PATCH v5 4/5] linux-custom: rewrite to no longer depend on the kernel's builddeb

[Jan Kiszka <jan.kiszka@siemens.com>]

On 10.12.19 19:22, [ext] Jan Kiszka wrote:
> From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> 
> Regain control over the packaging of the Linux kernel by providing our
> own debian recipes (debian,{control,rules} files and friends) instead
> of using the kernel's builddeb script. This will allow generation of
> packages for "perf" (not included in this changeset) with per distro
> scheme (Debian and Ubuntu have differences) and maintain compatibility
> with upstream packages generated from different source packages but
> dependent on a certain deployment scheme (e.g. linux-base for Debian)
> 
> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> [Jan: continue to build kernel-headers for the host, add changelog entry]
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---

...

> diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
> index 712f52b..bf1646a 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -2,89 +2,183 @@
>  #
>  # This software is a part of ISAR.
>  # Copyright (c) Siemens AG, 2018
> +# Copyright (c) Mentor Graphics, a Siemens business, 2019
>  #
>  # SPDX-License-Identifier: MIT
>  
> -FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
> +# Settings that would typically be done from the custom kernel recipe
> +# -------------------------------------------------------------------
>  
> +CHANGELOG_V = "${PV}+${PR}"
>  DESCRIPTION ?= "Custom kernel"
> +MAINTAINER ?= "isar-users <isar-users@googlegroups.com>"
> +
> +KBUILD_DEPENDS ?= "build-essential:native, \
> +                   libelf-dev:native, \
> +                   libncurses-dev:native, \
> +                   libssl-dev:native, \
> +                   bc, \
> +                   bison, \
> +                   cpio, \
> +                   flex, \
> +                   git, \
> +                   kmod, \
> +                   libssl-dev,"
> +
> +KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, \
> +                          kmod, \
> +                          linux-base (>= 4.3~),"
> +
> +KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, \
> +                                  libssl1.1,"
> +
> +KERNEL_LIBC_DEV_DEPLOY ?= "0"
> +
> +# Settings that may be changed on a per distro, machine or layer basis
> +# --------------------------------------------------------------------
> +
> +KERNEL_LOCALVERSION ?= "-${KERNEL_NAME_PROVIDED}-${PR}"

It turns out that this is deviating from the old versioning and can
break downstream layers. Fixable downstream, but then it needs to be
documented (RECIPE-API-CHANGELOG).

However, do we want this new default?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux