Yocto Project Discussions
 help / color / mirror / Atom feed
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 19:46:47 +0100	[thread overview]
Message-ID: <6f3f3121-47be-4d6f-8dd3-e13ff402298d@bootlin.com> (raw)
In-Reply-To: <CANNYZj8DWHh2=N+96j8zNosNUC0in-yrbqyUU-7dHWSP=6fhBQ@mail.gmail.com>

Hi Alex,

On 22.12.23 at 17:04, Alexander Kanavin wrote:
> On Fri, 22 Dec 2023 at 16:24, Michael Opdenacker
> <michael.opdenacker@bootlin.com> wrote:
>> 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.
> You don't need new images, but you would have to define a new builder
> entry in config.json that would set DISTRO to poky-binary-distro, and
> then build exiting images, and do additional steps (e.g. publish the
> package feeds).


Thanks for these clarifications, that helps!
However, if the same images are built, but with different distro 
settings, I still need to figure out where they will be generated, 
unlike the images on https://downloads.yoctoproject.org/releases/yocto/.

Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2023-12-22 18:46 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
2023-12-22 16:04     ` Alexander Kanavin
2023-12-22 18:46       ` Michael Opdenacker [this message]

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=6f3f3121-47be-4d6f-8dd3-e13ff402298d@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