public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 1/4] set SOURCE_DATE_EPOCH in wic environment
Date: Wed, 25 Jan 2023 14:46:29 +0000	[thread overview]
Message-ID: <20230125144632.2099908-1-felix.moessbauer@siemens.com> (raw)

By setting the variable in the generate_wic_image task, all wic
utilities that support reproducible builds pick it up and operate
accordingly.

This also makes the boot.scr u-boot script reproducible, as the script
generation is triggered by the wic plugin rootfs-u-boot.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes/imagetypes_wic.bbclass | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/classes/imagetypes_wic.bbclass b/meta/classes/imagetypes_wic.bbclass
index 3869525b..6fadc3ce 100644
--- a/meta/classes/imagetypes_wic.bbclass
+++ b/meta/classes/imagetypes_wic.bbclass
@@ -170,6 +170,9 @@ generate_wic_image() {
     export FAKEROOTCMD=${FAKEROOTCMD}
     export BUILDDIR=${TOPDIR}
     export MTOOLS_SKIP_CHECK=1
+    if [ ! -z "${SOURCE_DATE_EPOCH}" ]; then
+        export SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH}"
+    fi
     mkdir -p ${IMAGE_ROOTFS}/../pseudo
     touch ${IMAGE_ROOTFS}/../pseudo/files.db
 
-- 
2.34.1


             reply	other threads:[~2023-01-25 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 14:46 Felix Moessbauer [this message]
2023-01-25 14:46 ` [PATCH 2/4] remove apt cache dirs from final rootfs Felix Moessbauer
2023-01-25 14:46 ` [PATCH 3/4] clean /tmp in rootfs postprocess Felix Moessbauer
2023-01-25 14:46 ` [PATCH 4/4] warn only once in case file timestamps are updated Felix Moessbauer
2023-02-01  6:21 ` [PATCH 1/4] set SOURCE_DATE_EPOCH in wic environment Uladzimir Bely

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=20230125144632.2099908-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.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