From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 1/7] template: Copy template attributes on transform
Date: Thu, 23 Dec 2021 06:05:51 +0100 [thread overview]
Message-ID: <20211223050557.28269-2-ubely@ilbers.de> (raw)
In-Reply-To: <20211223050557.28269-1-ubely@ilbers.de>
Output file should have exactly the same flags as input one,
which is usefull for the cases like debian/rules or other executables.
So we should copy this part of metadata after the conversion.
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
meta/classes/template.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/template.bbclass b/meta/classes/template.bbclass
index fb9d1186..e6bcc362 100644
--- a/meta/classes/template.bbclass
+++ b/meta/classes/template.bbclass
@@ -8,7 +8,7 @@ TEMPLATE_VARS ?= "PN PV DESCRIPTION HOMEPAGE MAINTAINER DISTRO_ARCH"
do_transform_template[vardeps] = "TEMPLATE_FILES ${TEMPLATE_VARS}"
python do_transform_template() {
- import subprocess, contextlib
+ import subprocess, contextlib, shutil
workdir = os.path.normpath(d.getVar('WORKDIR', True))
@@ -56,5 +56,7 @@ python do_transform_template() {
stdout=output, env=env))
if process.wait() != 0:
bb.fatal("processing of template failed")
+
+ shutil.copymode(template_file, output_file)
}
addtask do_transform_template after do_unpack
--
2.20.1
next prev parent reply other threads:[~2021-12-23 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 5:05 [PATCH 0/7] Avoid using shell environment during the build Uladzimir Bely
2021-12-23 5:05 ` Uladzimir Bely [this message]
2021-12-23 5:05 ` [PATCH 2/7] linux-module: Do not use shell environment Uladzimir Bely
2021-12-23 5:05 ` [PATCH 3/7] u-boot: " Uladzimir Bely
2021-12-23 5:05 ` [PATCH 4/7] trusted-firmware: " Uladzimir Bely
2021-12-23 5:05 ` [PATCH 5/7] optee-os: " Uladzimir Bely
2021-12-23 5:05 ` [PATCH 6/7] kselftest: " Uladzimir Bely
2021-12-23 5:05 ` [PATCH 7/7] linux-mainline: Move cfg fragment test to debian/rules 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=20211223050557.28269-2-ubely@ilbers.de \
--to=ubely@ilbers.de \
--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