From: "Paul Barker" <paul@pbarker.dev>
To: "Daniel Wagenknecht" <dwagenknecht@emlix.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [DRAFT PATCH v3 0/2] Add meta layer information to spdx
Date: Fri, 06 Nov 2026 12:23:38 +0000 [thread overview]
Message-ID: <DMO4IMDLZZZ6.1IIXHMBALKRU3@pbarker.dev> (raw)
In-Reply-To: <20261106115455.4141199-1-dwagenknecht@emlix.com>
On Fri Nov 6, 2026 at 11:54 AM GMT, Daniel Wagenknecht wrote:
> v3 of the patch series looking for feedback on the overall architecture. I
> worked out the problem in alias linking, so a major blocker is out of the way.
>
> Please continue to consider this as a draft for discussion only!
>
> During discussion on IRC some questions were raised especially regarding the
> interaction with sstate caching.
> The layer information is only part of `create_spdx`, not `create_recipe_spdx`.
> It is thus only added to the final image spdx documents, not to the individual
> recipe or packagage spdx document. Images and their spdx documents are always
> rebuild, so with this approach no additional rebuilds occur even if a layers
> revision changes.
>
> My still open questions are:
> * is the overall architecture reasonable/correct?
> * referring to layers is inconsistent across tooling. E.g. the core layer is
> either named `core` as defined by `BBFILE_COLLECTIONS` or `meta` as that is
> the layer directory in the openembedded-core repository.
> I chose the latter since that is what the utility function
> `oe.buildcfg.get_layer_revisions` returns. The package URL (PURL)
> implementation uses the other naming scheme though. Any thoughts on which
> should be chosen and why?
Hi Daniel,
It's worth thinking about how this will interact with the proposed
changes to how layer.conf will work [1] [2]. That should hopefully
improve consistency in how layers are referred to across tools, but may
also impact other parts of these patches.
[1]: https://lists.openembedded.org/g/openembedded-architecture/topic/layers_and_layer_conf_time/121884200
[2]: https://lists.openembedded.org/g/openembedded-architecture/topic/layer_changes_poc_and_rfc/122113105
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-11-06 12:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:44 [PATCH 0/2] Add meta layer information to spdx Daniel Wagenknecht
2026-09-14 11:44 ` [PATCH 1/2] spdx: add entries for meta-layers Daniel Wagenknecht
2026-09-14 11:44 ` [PATCH 2/2] spdx: link files to the meta-layer providing them Daniel Wagenknecht
2026-09-15 8:02 ` [OE-core] [PATCH 0/2] Add meta layer information to spdx Antonin Godard
2026-09-15 13:04 ` [PATCH v2 " Daniel Wagenknecht
2026-09-16 7:08 ` [OE-core] " Antonin Godard
2026-09-16 8:45 ` Daniel Wagenknecht
2026-11-06 11:54 ` [DRAFT PATCH v3 " Daniel Wagenknecht
2026-11-06 11:54 ` [DRAFT PATCH v3 1/2] spdx: add entries for meta-layers Daniel Wagenknecht
2026-11-06 12:20 ` Paul Barker
2026-11-06 13:37 ` Daniel Wagenknecht
2026-11-06 11:54 ` [DRAFT PATCH v3 2/2] spdx: link files to the meta-layer providing them Daniel Wagenknecht
2026-11-06 12:23 ` Paul Barker [this message]
2026-11-10 23:32 ` [OE-core] [DRAFT PATCH v3 0/2] Add meta layer information to spdx Joshua Watt
2026-09-16 5:39 ` [PATCH v2 1/2] spdx: add entries for meta-layers Daniel Wagenknecht
2026-09-16 5:39 ` [PATCH v2 2/2] spdx: link files to the meta-layer providing them Daniel Wagenknecht
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=DMO4IMDLZZZ6.1IIXHMBALKRU3@pbarker.dev \
--to=paul@pbarker.dev \
--cc=dwagenknecht@emlix.com \
--cc=openembedded-core@lists.openembedded.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 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.