From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: Jan Kiszka <jan.kiszka@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 15:46:51 +0200 [thread overview]
Message-ID: <e3835c4e-5260-1212-e78a-6f4efa7e6514@siemens.com> (raw)
In-Reply-To: <f78de240-96d7-f5b7-b8ec-a61a99c8db48@siemens.com>
On 8/9/21 2:58 PM, Jan Kiszka wrote:
> 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.
>
We have the bootloader feature which is exclusive selected. So u-boot or
grub or efibootguard.
> 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?
>
I don't see others at the moment. The alternative would be make one
config for everything and only add the bootloader as configuration snippet.
> Jan
>
Quirin
next prev parent reply other threads:[~2021-08-09 13:46 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 ` [RFC PATCH 0/2] Add bbclass to generate build configuration from snippets Jan Kiszka
2021-08-09 13:46 ` Gylstorff Quirin [this message]
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=e3835c4e-5260-1212-e78a-6f4efa7e6514@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=christian.storm@siemens.com \
--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