From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Q. Gylstorff" <Quirin.Gylstorff@siemens.com>,
isar-users@googlegroups.com,
Christian Storm <christian.storm@siemens.com>
Subject: Re: [RFC PATCH 0/2] Add bbclass to generate build configuration from snippets
Date: Mon, 9 Aug 2021 14:58:25 +0200 [thread overview]
Message-ID: <f78de240-96d7-f5b7-b8ec-a61a99c8db48@siemens.com> (raw)
In-Reply-To: <20210809102645.17414-1-Quirin.Gylstorff@siemens.com>
On 09.08.21 12:26, Q. Gylstorff wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> This patchset adds the `build-config-snippets.bbclass`. This class can be used
> to generate package dependencies according to the used build configuration.
>
> It is in use as 'kconfig-snippets.bbclass' in [1] for the swupdate configuration.
>
Yeah, but working around the anti-distro properties of that packages. A
proper SWUpdate would build against all features and be configurable
during runtime.
Given that this is an anti pattern, I'm still not sure about what to do
with it. We are carrying it for SWUpdate for quite a while but that's
still the only user. Do we really see others? Or should we better invest
in fixing SWUpdate so that we can use its original Debian package, one day?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-08-09 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 10:26 Q. Gylstorff
2021-08-09 10:26 ` [RFC PATCH 1/2] Add build-config-snippet class Q. Gylstorff
2021-08-09 10:26 ` [RFC PATCH 2/2] Add example for build-config-snippets Q. Gylstorff
2021-08-09 12:58 ` Jan Kiszka [this message]
2021-08-09 13:46 ` [RFC PATCH 0/2] Add bbclass to generate build configuration from snippets Gylstorff Quirin
2021-08-09 14:05 ` Gylstorff Quirin
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=f78de240-96d7-f5b7-b8ec-a61a99c8db48@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Quirin.Gylstorff@siemens.com \
--cc=christian.storm@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