From: Zhihang Wei <wzh@ilbers.de>
To: Christoph Steiger <christoph.steiger@siemens.com>,
isar-users@googlegroups.com
Cc: felix.moessbauer@siemens.com, quirin.gylstorff@siemens.com,
clara.kowalsky@siemens.com
Subject: Re: [PATCH 1/1] linux-kernel: add cleandirs flag for tasks
Date: Wed, 13 May 2026 17:19:20 +0200 [thread overview]
Message-ID: <501fd93c-3be0-4a27-8c7e-f3ad9c3ddd15@ilbers.de> (raw)
In-Reply-To: <20260507120513.297817-1-christoph.steiger@siemens.com>
Applied to next, thanks.
Zhihang
On 5/7/26 14:05, 'Christoph Steiger' via isar-users wrote:
> Provide a cleandirs flag for directories that are used and expected to
> be empty during do_dpkg_source and do_prepare_build. This is the proper
> way to make sure directories exist and are empty.
>
> This also allows users to extend e.g. the do_dpkg_source functionality
> since that otherwise depends on the prepend order.
>
> Signed-off-by: Christoph Steiger <christoph.steiger@siemens.com>
> ---
> meta/classes-recipe/linux-kernel.bbclass | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes-recipe/linux-kernel.bbclass b/meta/classes-recipe/linux-kernel.bbclass
> index e3deac2d..55ea6d63 100644
> --- a/meta/classes-recipe/linux-kernel.bbclass
> +++ b/meta/classes-recipe/linux-kernel.bbclass
> @@ -240,9 +240,9 @@ def get_additional_build_profiles(d):
> KERNEL_LIBC_DEV_ARCH = "${@ bb.utils.contains('DEB_BUILD_PROFILES', 'pkg.{}.libcdev-arch-all'.format(d.getVar('BPN')), 'all\nMulti-Arch: foreign', 'any', d) }"
> DEB_BUILD_PROFILES += "${@get_additional_build_profiles(d)}"
>
> +do_prepare_build[cleandirs] += "${S}/debian"
> do_prepare_build:prepend() {
> # copy meta-data over to source tree
> - rm -rf ${S}/debian
> cp -r ${WORKDIR}/debian ${S}/
>
> # remove templates from the source tree
> @@ -308,7 +308,6 @@ dpkg_configure_kernel() {
> KERNEL_CONFIG_TARGET="${@get_kernel_config_target(d)}"
> EOF
>
> - rm -rf ${S}/${KERNEL_BUILD_DIR} && mkdir -p ${S}/${KERNEL_BUILD_DIR}
> if [ -n "${KERNEL_DEFCONFIG}" ]; then
> if [ -e "${WORKDIR}/${KERNEL_DEFCONFIG}" ]; then
> cp ${WORKDIR}/${KERNEL_DEFCONFIG} ${S}/${KERNEL_BUILD_DIR}/.config
> @@ -317,7 +316,6 @@ EOF
>
> # copy config fragments over to the kernel tree
> src_frags="${@ " ".join(config_fragments(d)) }"
> - rm -rf ${S}/debian/fragments
> for frag in ${src_frags}; do
> # skip frag if it starts with ${S}, thus is part of the sources
> if [ "${frag#${S}}" = "$frag" ]; then
> @@ -337,6 +335,7 @@ get_localversion_auto() {
> fi
> }
>
> +do_dpkg_source[cleandirs] += "${S}/${KERNEL_BUILD_DIR} ${S}/debian/fragments"
> do_dpkg_source:prepend() {
> dpkg_configure_kernel
> get_localversion_auto
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/501fd93c-3be0-4a27-8c7e-f3ad9c3ddd15%40ilbers.de.
prev parent reply other threads:[~2026-05-13 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 12:05 'Christoph Steiger' via isar-users
2026-05-13 15:19 ` Zhihang Wei [this message]
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=501fd93c-3be0-4a27-8c7e-f3ad9c3ddd15@ilbers.de \
--to=wzh@ilbers.de \
--cc=christoph.steiger@siemens.com \
--cc=clara.kowalsky@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@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