public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] poky.yaml.in: simplify host package requirements
Date: Thu, 8 Jun 2023 22:36:59 +0200	[thread overview]
Message-ID: <e1a49252-48b2-5159-ffb9-a23d7057263d@bootlin.com> (raw)
In-Reply-To: <175BA9792333BDA0.14539@lists.yoctoproject.org>

Hello,

On 03.05.23 at 16:46, Michael Opdenacker via lists.yoctoproject.org wrote:
>
> On 03.05.23 at 12:44, Richard Purdie wrote:
>>
>>>> Ideally there would be two levels of dependencies, those needed for 
>>>> the
>>>> basics and those needed to cover all the needs.
>>>>
>>>> Looking at the original bug, I think we did remove some of the
>>>> SDL/xterm/vnc requirements. Even then some vnc pieces are still needed
>>>> for some autobuilder setups though.
>>>>
>>>> We likely should define which workflows we expect to work with this
>>>> "essential" dependency list?
>>>
>>> Maybe we could document this elsewhere (in a section for developers /
>>> testers ?), to keep the list short for regular users.
>> I agree, I think we do likely need to have two different lists with
>> pointers to move the user to the appropriate one. Would you be able to
>> propose a change?
>
>
> Sure, but I'd need to know what commands I should test to figure out 
> which extra packages are needed.
>
> I'm asking because I suspect that some of the host packages we're 
> listing are no longer necessary anyway, either because of distro 
> changes, or because of our own changes. It's also good to document 
> what the host packages are necessary for.
>
> So, would you (or others) have such commands to run? I'd install the 
> "minimum" requirements first for each distro, and then run these 
> commands until I've found all the extra host packages they actually need.


So, any clue about the commands I should run to find the extra host 
packages that are needed to generate more than images, such as running 
Autobuilder and some testing jobs?

Anyway, if we document such extra host packages, we'll need to explain 
what they are needed for.
Thanks in advance
Cheers
Michael.

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



      parent reply	other threads:[~2023-06-08 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  9:01 [PATCH] poky.yaml.in: simplify host package requirements michael.opdenacker
2023-05-03  9:13 ` [docs] " Richard Purdie
2023-05-03  9:37   ` Michael Opdenacker
2023-05-03 10:44     ` Richard Purdie
2023-05-03 14:46       ` Michael Opdenacker
     [not found]       ` <175BA9792333BDA0.14539@lists.yoctoproject.org>
2023-06-08 20:36         ` 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=e1a49252-48b2-5159-ffb9-a23d7057263d@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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