From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH v6 0/5] linux-custom recipe rework
Date: Fri, 31 Jan 2020 09:57:13 +0100 [thread overview]
Message-ID: <20200131095713.36f558df@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <cover.1576696264.git.jan.kiszka@siemens.com>
Hi,
where did the "apt-get" go that was in the inc? A review of the
base-apt series found custom kernel apt-gets missing in the caching,
now my fix can not be rebased on top of this.
Is it now just "regular" dpkg doing the builddeps? If that is the case
my base-apt series does not need a fix after all.
Henning
On Wed, 18 Dec 2019 20:10:59 +0100
"[ext] Jan Kiszka" <jan.kiszka@siemens.com> wrote:
> Changes in this round:
>
> - decoupled recipe version from kernel version
> (permits also "latest" recipes)
> - renamed KERNEL_LOCALVERSION to LINUX_VERSION_EXTENSION
> (aligns us with yocto)
> - made LINUX_VERSION_EXTENSION optional and empty by default
> (backward compatible)
> - removed KERNEL_DTB_DIR and KERNEL_HEADERS_DIR customizability
> (simplifies the decoupling of versions, but also lacks use case)
> - added RECIPE-API-CHANGELOG for LINUX_VERSION_EXTENSION
> - set LINUX_VERSION_EXTENSION in linux-mainline recipe as test case
> - added GPL reference and stable URL to Debian install scripts
>
> As the deviations in patch 4 are too significant by now, I've adopted
> it completely, providing credit to Cedric's foundation work in the
> changelog.
>
> Jan
>
>
> CC: Cedric Hombourger <Cedric_Hombourger@mentor.com>
>
> Cedric Hombourger (3):
> recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree
> defconfigs linux-mainline: fix stripping of .0 from the kernel version
> linux-mainline: update from 4.19.0 to 4.19.88
>
> Jan Kiszka (2):
> linux-custom: rewrite to no longer depend on the kernel's builddeb
> linux-mainline: Test config fragments and LINUX_VERSION_EXTENSION
>
> RECIPE-API-CHANGELOG.md | 15 ++
> doc/custom_kernel.md | 83 +++++++++
> .../recipes-kernel/linux/files/no-root-nfs.cfg | 1 +
> .../recipes-kernel/linux/files/no-ubifs-fs.cfg | 1 +
> .../recipes-kernel/linux/linux-mainline_4.19.0.bb | 22 ---
> .../recipes-kernel/linux/linux-mainline_4.19.88.bb | 35 ++++
> meta/recipes-kernel/linux/files/build-kernel.sh | 129
> ------------- meta/recipes-kernel/linux/files/debian/compat |
> 1 + .../recipes-kernel/linux/files/debian/control.tmpl | 37 ++++
> .../linux/files/debian/isar/build.tmpl | 40 ++++
> .../linux/files/debian/isar/clean.tmpl | 21 +++
> .../linux/files/debian/isar/common.tmpl | 49 +++++
> .../linux/files/debian/isar/install.tmpl | 191
> +++++++++++++++++++ .../linux/files/debian/isar/version.cfg.tmpl
> | 2 + .../linux/files/debian/linux-image.postinst.tmpl | 30 +++
> .../linux/files/debian/linux-image.postrm.tmpl | 36 ++++
> .../linux/files/debian/linux-image.preinst.tmpl | 26 +++
> .../linux/files/debian/linux-image.prerm.tmpl | 22 +++
> meta/recipes-kernel/linux/files/debian/rules.tmpl | 39 ++++
> meta/recipes-kernel/linux/linux-custom.inc | 207
> +++++++++++++++------ 20 files changed, 782 insertions(+), 205
> deletions(-) create mode 100644 doc/custom_kernel.md
> create mode 100644
> meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg create mode
> 100644 meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg delete
> mode 100644 meta-isar/recipes-kernel/linux/linux-mainline_4.19.0.bb
> create mode 100644
> meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb delete mode
> 100644 meta/recipes-kernel/linux/files/build-kernel.sh create mode
> 100644 meta/recipes-kernel/linux/files/debian/compat create mode
> 100644 meta/recipes-kernel/linux/files/debian/control.tmpl create
> mode 100644 meta/recipes-kernel/linux/files/debian/isar/build.tmpl
> create mode 100644
> meta/recipes-kernel/linux/files/debian/isar/clean.tmpl create mode
> 100644 meta/recipes-kernel/linux/files/debian/isar/common.tmpl create
> mode 100644 meta/recipes-kernel/linux/files/debian/isar/install.tmpl
> create mode 100644
> meta/recipes-kernel/linux/files/debian/isar/version.cfg.tmpl create
> mode 100644
> meta/recipes-kernel/linux/files/debian/linux-image.postinst.tmpl
> create mode 100644
> meta/recipes-kernel/linux/files/debian/linux-image.postrm.tmpl create
> mode 100644
> meta/recipes-kernel/linux/files/debian/linux-image.preinst.tmpl
> create mode 100644
> meta/recipes-kernel/linux/files/debian/linux-image.prerm.tmpl create
> mode 100755 meta/recipes-kernel/linux/files/debian/rules.tmpl
>
next prev parent reply other threads:[~2020-01-31 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 19:10 Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 1/5] recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree defconfigs Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 2/5] linux-mainline: fix stripping of .0 from the kernel version Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 3/5] linux-mainline: update from 4.19.0 to 4.19.88 Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 4/5] linux-custom: rewrite to no longer depend on the kernel's builddeb Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 5/5] linux-mainline: Test config fragments and LINUX_VERSION_EXTENSION Jan Kiszka
2019-12-26 15:51 ` [PATCH v6 0/5] linux-custom recipe rework Baurzhan Ismagulov
2020-01-31 8:57 ` Henning Schild [this message]
2020-01-31 9:04 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200131095713.36f558df@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox