From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Antonin Godard <antonin.godard@bootlin.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [bitbake-devel] [PATCH] bitbake-setup: replace {THISDIR} token with an explicit keyword
Date: Fri, 07 Nov 2025 09:55:38 +0000 [thread overview]
Message-ID: <daa19e97cfc92bdfdfdebc0b344dc11c6462d0fc.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_qwFt6F-LEwMqe0D04dy7t9_FJMWf1tpCUZ0bayfdUZQ@mail.gmail.com>
On Fri, 2025-11-07 at 04:32 +0100, Alexander Kanavin wrote:
> On Fri 7. Nov 2025 at 1.59, Peter Kjellerstedt <peter.kjellerstedt@axis.com> wrote:
> >
> > >
> > > bb-layers-relative maybe?
> > >
> > > bb-layers-relative-to-this-file is precise but does feel a bit too
> > > unwieldy. Any other options?
> > >
> > > Cheers,
> > >
> > > Richard
> >
> > After I saw Alex' patch for bitbake-setup.schema.json:
> > https://lore.kernel.org/openembedded-core/20251106170815.2439421-1-alex.kanavin@gmail.com/T/#u
> > it made me realize that I had not thought that paths in both
> > bb-layers and bb-layers-relative are actually relative, just to
> > different locations. Unfortunately, I think the newly suggested
> > name is then misleading as it implies that paths in bb-layers
> > are not relative. :( I now also understand why the longer
> > bb-layers-relative-to-this-file was originally proposed.
> >
> > I don't have a good solution for this. The best I can come up
> > with is to rename them both to, e.g., bb-layers-dir-relative and
> > bb-layers-file-relative
>
> I tend to agree. I’d rather call them ‘bb-layers-in-sources’ and ‘bb-
> layers-in-this-dir’. Patch is coming even though I’m technically on
> holiday since midnight. This is important.
I don't agree with "sources" in here.
I think if we call them:
bb-layers
and
bb-layers-file-relative
then this should be ok? I agree we need to get this right.
Cheers,
Richard
next prev parent reply other threads:[~2025-11-07 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 11:47 [PATCH] bitbake-setup: replace {THISDIR} token with an explicit keyword Alexander Kanavin
2025-11-06 12:11 ` [bitbake-devel] " Antonin Godard
2025-11-06 12:28 ` Alexander Kanavin
2025-11-06 15:15 ` Richard Purdie
2025-11-06 15:26 ` Robert P. J. Day
2025-11-06 17:09 ` Alexander Kanavin
2025-11-07 0:59 ` Peter Kjellerstedt
2025-11-07 3:32 ` Alexander Kanavin
2025-11-07 9:55 ` Richard Purdie [this message]
2025-11-07 10:14 ` Alexander Kanavin
2025-11-07 10:17 ` Richard Purdie
2025-11-07 10:20 ` Alexander Kanavin
2025-11-07 13:18 ` Richard Purdie
[not found] ` <18759C05E6F46C57.499307@lists.openembedded.org>
2025-11-07 8:07 ` Alexander Kanavin
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=daa19e97cfc92bdfdfdebc0b344dc11c6462d0fc.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.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 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.