From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Paul Barker" <paul@pbarker.dev>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH] contributor-guide/recipe-style-guide.rst: explain difference between layer and recipe license(s)
Date: Fri, 09 Jan 2026 10:30:15 +0100 [thread overview]
Message-ID: <DFJYBWC4AGNZ.2X8V6CNOZCOAN@bootlin.com> (raw)
In-Reply-To: <76a20da7b564f312a1179d8fa955c6245f44ec98.camel@pbarker.dev>
Hi,
On Thu Jan 8, 2026 at 3:47 PM CET, Paul Barker wrote:
[...]
> Other layers may want to handle metadata licenses in different ways, for
> example by including an SPDX-License-Identifier comment at the top of
> recipe files. So I think we should keep this note more generic.
>
> Setting a :term:`LICENSE` in a recipe applies to the software to be
> built by this recipe, not to the recipe file itself. The license of
> recipes, configuration files and scripts should also be clearly
> specified, for example via comments or via a license found in the
> :term:`layer` that holds these files. These license files are usually
> found at the root of the layer. Exceptions should be clearly stated in
> the layer README or LICENSE file.
>
> For example, the :term:`OpenEmbedded-Core (OE-Core)` layer provides both
> the GPL-2.0-only and MIT license files, and a "LICENSE" file to explain
> how these two licenses are attributed to files found in the layer.
>
> How does that look?
Looks great, that makes sense indeed. I'll send a new version. Thanks!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-01-09 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:30 [PATCH] contributor-guide/recipe-style-guide.rst: explain difference between layer and recipe license(s) Antonin Godard
2026-01-08 14:47 ` [docs] " Paul Barker
2026-01-09 9:30 ` Antonin Godard [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=DFJYBWC4AGNZ.2X8V6CNOZCOAN@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=paul@pbarker.dev \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox