From: roberto.foglietta@linuxteam.org
To: isar-users@googlegroups.com
Cc: roberto.foglietta@gmail.com, Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] imagetypes XZ_OPTIONS replaced by XZ_DEFAULTS defined in bitbake.comf
Date: Thu, 9 Feb 2023 23:41:48 +0100 [thread overview]
Message-ID: <20230209224148.60152-1-roberto.foglietta@linuxteam.org> (raw)
From: Anton Mikanovich <amikan@ilbers.de>
imagetypes, bugfix
A previous patch moved XZ_ variables declarations into bitbake.conf from
the imagetypes class. In such patch the XZ_OPTIONS has been renamed in
XZ_DEFAULTS but the XZ_ command in imagetype class has not been updated.
This patch fixed this bug which decreases performance and alters the
expected behaviour.
Requires:
* bitbake.conf: declare default XZ and ZSTD options
Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
---
meta/classes/imagetypes.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/imagetypes.bbclass b/meta/classes/imagetypes.bbclass
index 0cff440f..7d193d2e 100644
--- a/meta/classes/imagetypes.bbclass
+++ b/meta/classes/imagetypes.bbclass
@@ -98,5 +98,5 @@ IMAGE_CONVERSIONS = "gz xz"
CONVERSION_CMD:gz = "${SUDO_CHROOT} sh -c 'gzip -f -9 -n -c --rsyncable ${IMAGE_FILE_CHROOT} > ${IMAGE_FILE_CHROOT}.gz'"
CONVERSION_DEPS:gz = "gzip"
-CONVERSION_CMD:xz = "${SUDO_CHROOT} sh -c 'xz -c ${XZ_OPTIONS} ${IMAGE_FILE_CHROOT} > ${IMAGE_FILE_CHROOT}.xz'"
+CONVERSION_CMD:xz = "${SUDO_CHROOT} sh -c 'xz -c ${XZ_DEFAULTS} ${IMAGE_FILE_CHROOT} > ${IMAGE_FILE_CHROOT}.xz'"
CONVERSION_DEPS:xz = "xz-utils"
--
2.34.1
next reply other threads:[~2023-02-09 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 22:41 roberto.foglietta [this message]
2023-02-10 10:27 ` Henning Schild
2023-02-10 10:31 ` Henning Schild
2023-02-10 11:15 ` Roberto A. Foglietta
2023-02-10 11:28 ` Henning Schild
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=20230209224148.60152-1-roberto.foglietta@linuxteam.org \
--to=roberto.foglietta@linuxteam.org \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.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