From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: yocto@lists.yoctoproject.org,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH yocto-autobuilder-helper v2] config.json: add "package-management" to images
Date: Fri, 22 Dec 2023 16:24:07 +0100 [thread overview]
Message-ID: <e6174a7a-2981-4b88-a24e-e6f72873886b@bootlin.com> (raw)
In-Reply-To: <CANNYZj-iEw6aV1Ki6BOu-xRVxKSmFvGS-thU_13NS99b8Tt_gA@mail.gmail.com>
Hi Alex,
On 22.12.23 at 15:13, Alexander Kanavin wrote:
> Thanks for explaining - I would instead make a 'poky-binary-distro'
> distro configuration in meta-poky, and collect all needed settings in
> there.
>
> Placing this in config.json significantly changes how all of the
> images on autobuilder are assembled and tested, particularly there is
> no testing of images without package management anymore.
>
> I would in general want to avoid adding any further 'global tweaks'
> that override oe-core or poky defaults.
Thanks for your advice! Actually, I wasn't sure how to make the change.
If I understand correctly, even after I define a new
'poky-binary-distro' distro in meta-poky (if agreed), I'll still have to
add a new image to config.json, but indeed not touching existing ones.
Richard, would you be open to this suggestion?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-12-22 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 13:19 [PATCH yocto-autobuilder-helper v2] config.json: add "package-management" to images michael.opdenacker
2023-12-22 14:13 ` Alexander Kanavin
2023-12-22 15:24 ` Michael Opdenacker [this message]
2023-12-22 16:04 ` Alexander Kanavin
2023-12-22 18:46 ` Michael Opdenacker
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=e6174a7a-2981-4b88-a24e-e6f72873886b@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@lists.yoctoproject.org \
/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