mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-07-15 15:37:03 +00:00
Code Issues Projects Releases Wiki Activity

recipe-style-guide: Clarify when License-Update tag is needed

Browse Source 
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 <paul@pbarker.dev>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit db04faf56afded6c5f846cc60a9062e0a1ffa741)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Paul Barker <paul@pbarker.dev>
This commit is contained in:
Paul Barker
2026-06-30 08:55:34 +01:00
parent bb98354685
commit a448bff87a
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/contributor-guide/recipe-style-guide.rst
+7 -2
View File
@@ -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
---------------------------------------