From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 0/9] Avoid using shell environment during the build
Date: Tue, 25 Jan 2022 16:51:32 +0300 [thread overview]
Message-ID: <2755364.Ex9A2HvPv6@home> (raw)
In-Reply-To: <9ccd085b-7649-c856-dab7-3d959bb4141c@siemens.com>
In the email from вторник, 25 января 2022 г. 16:29:28 +03 user Jan Kiszka
wrote:
> On 25.01.22 13:32, Uladzimir Bely wrote:
> > This patchset is a subseries of 'Sbuild/Schroot migration' patchset
> > including only preparation patches. It doesn't require any changes
> > in host machine configuration for downstreams (meta-iot2050 and
> > xenomai-images were tested) so can be merged independently.
> >
> > In this patchset the main topic is a migration to template files that
> > allows to use cleaner build environment.
> >
> > When this patchset is merged, it will make maintenance of remaining
> > sbuild-related patches easier and will shorten their number.
> >
> > Changes since v1:
> > - Introduced `dpkg_build_export` function to be used for passing
> > variables to build environment;
>
> I wonder - as just written in the iot2050 PR - if we have any chance to
> detect old exports and warn the user if their recipes need to be
> converted to dpkg_build_export. Any ideas?
>
> Jan
>
That's an interesting question. If we could make a hook that could intercept
any 'export' call in dpkg_runbuild (usually, in _prepend), we could make a
warning. On the other hand, in this case we could not introduce a new
function, but just do what we really need instead of doing shell export.
For now I have no ideas how we could do it.
> > - Linux kernel framgments handling is done in Debian way.
> >
> > Anton Mikanovich (6):
> > linux-module: Do not use shell environment
> > u-boot: Do not use shell environment
> > trusted-firmware: Do not use shell environment
> > optee-os: Do not use shell environment
> > kselftest: Do not use shell environment
> > linux-mainline: Move cfg fragment test to debian/rules
> >
> > Uladzimir Bely (3):
> > template: Copy template attributes on transform
> > dpkg: Use a specific export function in pre-build tasks
> > linux-custom: Move cfg fragments applying to debian/rules
> >
> > meta-isar/recipes-app/hello/hello.bb | 2 +-
> > .../optee-os/optee-os-stm32mp15x_3.11.0.bb | 2 +-
> > .../linux/linux-mainline_5.4.70.bb | 16 +++---
> > meta/classes/dpkg-base.bbclass | 9 ++++
> > meta/classes/dpkg.bbclass | 2 +-
> > meta/classes/template.bbclass | 4 +-
> > .../libubootenv/libubootenv_0.3-3.bb | 2 +-
> > .../files/debian/{rules => rules.tmpl} | 4 +-
> > meta/recipes-bsp/optee-os/optee-os-custom.inc | 9 +---
> > .../files/debian/{rules => rules.tmpl} | 4 +-
> > .../trusted-firmware-a-custom.inc | 9 +---
> > .../u-boot/files/debian/{rules => rules.tmpl} | 2 +-
> > meta/recipes-bsp/u-boot/u-boot-custom.inc | 9 +---
> > .../kselftest/files/{rules => rules.tmpl} | 0
> > meta/recipes-kernel/kselftest/kselftest.inc | 21 +++-----
> > .../linux-module/files/debian/rules | 37 -------------
> > .../linux-module/files/debian/rules.tmpl | 52 +++++++++++++++++++
> > meta/recipes-kernel/linux-module/module.inc | 19 ++-----
> > .../linux/files/debian/isar/configure.tmpl | 19 +++++++
> > .../linux/files/debian/rules.tmpl | 3 ++
> > meta/recipes-kernel/linux/linux-custom.inc | 14 ++---
> > 21 files changed, 125 insertions(+), 114 deletions(-)
> > rename meta/recipes-bsp/optee-os/files/debian/{rules => rules.tmpl}
> > (75%)
> > rename meta/recipes-bsp/trusted-firmware-a/files/debian/{rules =>
> > rules.tmpl} (77%) rename meta/recipes-bsp/u-boot/files/debian/{rules =>
> > rules.tmpl} (94%) rename meta/recipes-kernel/kselftest/files/{rules =>
> > rules.tmpl} (100%) delete mode 100755
> > meta/recipes-kernel/linux-module/files/debian/rules create mode 100755
> > meta/recipes-kernel/linux-module/files/debian/rules.tmpl create mode
> > 100644 meta/recipes-kernel/linux/files/debian/isar/configure.tmpl
next prev parent reply other threads:[~2022-01-25 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 12:32 Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 1/9] template: Copy template attributes on transform Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 2/9] linux-module: Do not use shell environment Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 3/9] u-boot: " Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 4/9] trusted-firmware: " Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 5/9] optee-os: " Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 6/9] kselftest: " Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 7/9] linux-mainline: Move cfg fragment test to debian/rules Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 8/9] dpkg: Use a specific export function in pre-build tasks Uladzimir Bely
2022-01-25 12:32 ` [PATCH v2 9/9] linux-custom: Move cfg fragments applying to debian/rules Uladzimir Bely
2022-01-25 13:29 ` [PATCH v2 0/9] Avoid using shell environment during the build Jan Kiszka
2022-01-25 13:51 ` Uladzimir Bely [this message]
2022-01-25 13:55 ` 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=2755364.Ex9A2HvPv6@home \
--to=ubely@ilbers.de \
--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