public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH 1/1] rootfs: do not clean pycache for distros that build it reproducible
Date: Mon, 14 Sep 2026 14:33:00 +0200	[thread overview]
Message-ID: <ebf26361-14e1-4c6c-ac59-c406d9fe339b@ilbers.de> (raw)
In-Reply-To: <20260907113533.3937376-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

Zhihang

On 9/7/26 13:35, 'Felix Moessbauer' via isar-users wrote:
> The reproducible builds issues in the pycache have finally been solved
> and the corresponding fixes are available from bookworm on.
> By that, we no longer drop the pycache for distros that build it
> reproducibly, as this speeds up first-time invocations of python tools
> in the rootfs. This is especially relevant in cases where the pycache
> cannot be written at all, e.g. because the rootfs is read only mounted.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>   meta/classes-recipe/rootfs.bbclass | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
> index cf996f5c..20ce7d83 100644
> --- a/meta/classes-recipe/rootfs.bbclass
> +++ b/meta/classes-recipe/rootfs.bbclass
> @@ -46,8 +46,11 @@ ROOTFS_FEATURES_REPRODUCIBLE = " \
>       clean-package-cache \
>       clean-log-files \
>       clean-debconf-cache \
> -    clean-pycache \
>   "
> +ROOTFS_FEATURES_REPRODUCIBLE:append:buster = " clean-pycache"
> +ROOTFS_FEATURES_REPRODUCIBLE:append:bullseye = " clean-pycache"
> +ROOTFS_FEATURES_REPRODUCIBLE:append:focal = " clean-pycache"
> +
>   ROOTFS_FEATURES += "${ROOTFS_FEATURES_REPRODUCIBLE}"
>   
>   # only supported from bookworm / jammy on

-- 
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/ebf26361-14e1-4c6c-ac59-c406d9fe339b%40ilbers.de.

      reply	other threads:[~2026-09-14 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 11:35 'Felix Moessbauer' via isar-users
2026-09-14 12:33 ` 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=ebf26361-14e1-4c6c-ac59-c406d9fe339b@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=felix.moessbauer@siemens.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