From: Trevor Woerner <twoerner@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] ref-manual/variables.rst: document WIC_CREATE_EXTRA_ARGS
Date: Tue, 13 May 2025 09:14:35 -0400 [thread overview]
Message-ID: <20250513131435.GA31516@localhost> (raw)
In-Reply-To: <788da1ca-6e56-41ed-8814-4771710bfb69@cherry.de>
On Tue 2025-05-13 @ 09:59:58 AM, Quentin Schulz wrote:
> Hi Trevor,
>
> On 5/12/25 11:01 PM, Trevor Woerner wrote:
> > On Mon 2025-05-12 @ 09:31:27 AM, Quentin Schulz wrote:
> > > Hi Trevor,
> > >
> > > On 5/6/25 7:23 PM, Trevor Woerner via lists.yoctoproject.org wrote:
>
> [...]
>
> > > > + image recipe. As part of this process the Wic bbclass will call the
> > >
> > > There's no wic bbclass.
> >
> > I know. That's why I didn't write "wic.bbclass". I wrote, generically, the Wic
> > bbclass.
> >
> > > I think you meant to say image_types_wic bbclass? It
> > > would be nice to provide a :ref: there but we actually do not have the class
> > > explained yet so cannot do a :ref:`ref-classes-image_types_wic` like we
> > > could for image_types.
> >
> > I didn't want to give a specific name and wanted to write something that would
> > be immune from changes in the bbclass's name. Also, layers might implement
> > their own bbclass that uses wic, so I wanted to include those as well.
> >
>
> If they have their own bbclass that uses wic, they wouldn't necessarily be
> using WIC_CREATE_EXTRA_ARGS as this variable is specific to
> image_types_wic.bbclass, we also already list the name of some classes so it
> isn't a new problem.
I'll just rewrite the part to avoid mentioning the bbclass. How the command is
invoked is irrelevant.
prev parent reply other threads:[~2025-05-13 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:23 [PATCH] ref-manual/variables.rst: document WIC_CREATE_EXTRA_ARGS Trevor Woerner
2025-05-12 7:31 ` [docs] " Quentin Schulz
2025-05-12 21:01 ` Trevor Woerner
2025-05-13 7:59 ` Quentin Schulz
2025-05-13 13:14 ` Trevor Woerner [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=20250513131435.GA31516@localhost \
--to=twoerner@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.