From: Justin Bronder <jsbronder@cold-front.org>
To: docs@lists.yoctoproject.org
Cc: Justin Bronder <jsbronder@cold-front.org>
Subject: [PATCH] contributor-guide: add License-Update tag
Date: Tue, 21 Nov 2023 14:58:54 -0500 [thread overview]
Message-ID: <20231121195854.27968-1-jsbronder@cold-front.org> (raw)
Porting from the old wiki
https://www.openembedded.org/index.php?title=Commit_Patch_Message_Guidelines&oldid=10935#Describing_license_changes
Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
---
.../contributor-guide/recipe-style-guide.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst
index a005aa324..bb8f6980e 100644
--- a/documentation/contributor-guide/recipe-style-guide.rst
+++ b/documentation/contributor-guide/recipe-style-guide.rst
@@ -250,6 +250,17 @@ Recipes need to define both the :term:`LICENSE` and
correct string that you can substitute into the recipe file for a
subsequent build.
+License Updates
++++++++++++++++
+When you change the :term:`LICENSE` or :term:`LIC_FILES_CHKSUM` in the recipe
+you need to briefly explain the reason for the change via a ``License-Update:``
+tag. Often it's quite trivial, such as::
+
+ License-Update: copyright years refreshed
+
+Less often, the actual licensing terms themselves will have changed. If so, do
+try to link to upstream making/justifying that decision.
+
Tips and Guidelines for Writing Recipes
---------------------------------------
--
2.42.0
next reply other threads:[~2023-11-21 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 19:58 Justin Bronder [this message]
2023-11-22 20:23 ` [docs] [PATCH] contributor-guide: add License-Update tag Michael Opdenacker
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=20231121195854.27968-1-jsbronder@cold-front.org \
--to=jsbronder@cold-front.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).