From: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>
To: jan.kiszka@siemens.com, felix.moessbauer@siemens.com,
cip-dev@lists.cip-project.org
Subject: [cip-dev][isar-cip-core][PATCH] layer.conf: Move SOURCE_EPOCH to kas-cip.yml
Date: Mon, 8 Apr 2024 14:44:59 +0200 [thread overview]
Message-ID: <20240408124535.300693-1-Quirin.Gylstorff@siemens.com> (raw)
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
This allows downstream layers to overwrite the SOURCE_DATE_EPOCH with
there own implementation.
Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
Was there an reason for the 'Immediate variable expansion' `:=`?
In the shell the variable is expanded correctly.
conf/layer.conf | 1 -
kas-cip.yml | 2 ++
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 82b4084..6198e1b 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -25,4 +25,3 @@ LAYERDIR_cip-core[vardepvalue] = "isar-cip-core"
IMAGE_CLASSES += "squashfs verity swupdate"
-SOURCE_DATE_EPOCH := "${@bb.process.run("git -C ${LAYERDIR_cip-core} log -1 --pretty=%ct | tr -d '\n'")[0]}"
diff --git a/kas-cip.yml b/kas-cip.yml
index d10161f..737cfa0 100644
--- a/kas-cip.yml
+++ b/kas-cip.yml
@@ -41,6 +41,8 @@ local_conf_header:
USERS += "root"
USER_root[password] = "root"
USER_root[flags] = "clear-text-password"
+ source_epoch: |
+ SOURCE_DATE_EPOCH := "${@bb.process.run("git -C ${LAYERDIR_cip-core} log -1 --pretty=%ct | tr -d '\n'")[0]}"
env:
DISTRO_APT_PREMIRRORS: ""
--
2.43.0
next reply other threads:[~2024-04-08 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 12:44 Quirin Gylstorff [this message]
2024-04-08 14:24 ` [cip-dev][isar-cip-core][PATCH] layer.conf: Move SOURCE_EPOCH to kas-cip.yml MOESSBAUER, Felix
2024-04-08 17:27 ` 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=20240408124535.300693-1-Quirin.Gylstorff@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).