From: chee.yang.lee@intel.com
To: docs@lists.yoctoproject.org
Subject: [PATCH 1/3] release-notes-5.0: update license section
Date: Fri, 12 Apr 2024 18:19:55 +0800 [thread overview]
Message-ID: <20240412101957.2071854-2-chee.yang.lee@intel.com> (raw)
In-Reply-To: <20240412101957.2071854-1-chee.yang.lee@intel.com>
From: Lee Chee Yang <chee.yang.lee@intel.com>
also re-order license.
Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
---
documentation/migration-guides/release-notes-5.0.rst | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/documentation/migration-guides/release-notes-5.0.rst b/documentation/migration-guides/release-notes-5.0.rst
index 2f39fda41..0a0e4e5f3 100644
--- a/documentation/migration-guides/release-notes-5.0.rst
+++ b/documentation/migration-guides/release-notes-5.0.rst
@@ -232,8 +232,16 @@ Recipe License changes in 5.0
The following corrections have been made to the :term:`LICENSE` values set by recipes:
-- ``systemd``: make the scope of ``LGPL`` more accurate (``LGPL-2.1`` -> ``LGPL-2.1-or-later``)
-- ``libsystemd``: set its own :term:`LICENSE` value (``LGPL-2.1-or-later``) to add more granularity
+- ``elfutils``: split license for libraries & backend and utilities.
+- ``ghostscript``: correct :term:`LICENSE` to ``AGPL-3.0-or-later``.
+- ``libsystemd``: set its own :term:`LICENSE` value (``LGPL-2.1-or-later``) to add more granularity.
+- ``libtest-warnings-perl``: update :term:`LICENSE` ``Artistic-1.0`` to ``Artistic-1.0-Perl``.
+- ``linux-firmware``: set package :term:`LICENSE` appropriately for carl9170, rockchip and powerpr.
+- ``newlib``: add license ``Apache-2.0-with-LLVM-exception``.
+- ``python3-poetry-core``: add license ``BSD-3-Claus`` for fastjsonschema.
+- ``systemd``: make the scope of ``LGPL`` more accurate (``LGPL-2.1`` -> ``LGPL-2.1-or-later``).
+- ``util-linux``: add ``GPL-1.0-or-later`` license for fdisk and ``MIT`` license for flock.
+- ``zstd``: set to dual-licensed ``BSD-3-Clause`` or ``GPL-2.0-only``.
Security Fixes in 5.0
~~~~~~~~~~~~~~~~~~~~~
--
2.34.1
next prev parent reply other threads:[~2024-04-12 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 10:19 [PATCH 0/3] release-notes-5.0: update license, bitbake and devtool chee.yang.lee
2024-04-12 10:19 ` chee.yang.lee [this message]
2024-04-12 10:19 ` [PATCH 2/3] release-notes-5.0: update bitbake improvement chee.yang.lee
2024-04-12 13:05 ` [docs] " Michael Opdenacker
2024-04-12 10:19 ` [PATCH 3/3] release-notes-5.0: add devtool improvement chee.yang.lee
2024-04-12 13:10 ` [docs] " 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=20240412101957.2071854-2-chee.yang.lee@intel.com \
--to=chee.yang.lee@intel.com \
--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).