From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: are there any actual "container layers" left?
Date: Mon, 16 Jun 2025 08:49:34 -0400 (EDT) [thread overview]
Message-ID: <fdb50d7e-bd02-e3eb-e320-19814e9aa929@crashcourse.ca> (raw)
perusing the BSP developer's guide:
https://docs.yoctoproject.org/bsp-guide/bsp.html
and early on, there is a reference to "container layers," which i
remember because i recall bringing up the issue of how to refer to OE
layers that were themselves layers while containing even *more* layers
as subdirectories.
first, since this is the BSP guide, it's a bit weird to use
meta-openembedded as an alleged example of a container layer. but
that's not the issue.
as i recall, the phrase "container layer" was meant to describe
something which was itself a valid layer, while containing further
valid layers; if memory serves, "meta-intel" used to look like that.
but that's not what it looks like anymore, it's just a regular layer:
https://git.yoctoproject.org/meta-intel/tree/
as another example, the "meta-xilinx" checkout clearly fetches
numerous layers, but it itself is not a layer, so it doesn't fit the
definition of a "container layer".
is this terminology still useful? and under what circumstances?
rday
reply other threads:[~2025-06-16 12:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fdb50d7e-bd02-e3eb-e320-19814e9aa929@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=docs@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