From a448bff87a369a865a1112d28ffc3847b1df804f Mon Sep 17 00:00:00 2001 From: Paul Barker Date: Tue, 30 Jun 2026 08:55:34 +0100 Subject: [PATCH] recipe-style-guide: Clarify when License-Update tag is needed As discussed in a patch review call, we don't need License-Update tags in commits where the upstream license has not changed, and we are instead changing the LICENSE variable to fix incorrect data. (From yocto-docs rev: d4e19136ffee4fabfdfc5048835da64f0cfbb3eb) Signed-off-by: Paul Barker Signed-off-by: Antonin Godard (cherry picked from commit db04faf56afded6c5f846cc60a9062e0a1ffa741) Signed-off-by: Antonin Godard Signed-off-by: Paul Barker --- documentation/contributor-guide/recipe-style-guide.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst index 07f7a58c18..bde1da7ded 100644 --- a/documentation/contributor-guide/recipe-style-guide.rst +++ b/documentation/contributor-guide/recipe-style-guide.rst @@ -268,14 +268,19 @@ 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:: +due to upstream making modifications to the license files, 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. +The ``License-Update:`` tag is not needed for commits which fix incorrect +license data in our metadata (for an example see OE-Core commit +:oecore_rev:`6c8b76d240d2457578a58787121bc5873d724ee2`). + Tips and Guidelines for Writing Recipes ---------------------------------------