Hi,

Most likely those:

$ git grep -E 'LICENSE.*-with-'
meta/recipes-connectivity/socat/socat_1.8.0.0.bb:LICENSE =
"GPL-2.0-with-OpenSSL-exception"
meta/recipes-core/newlib/newlib.inc:LICENSE = "GPL-2.0-only & LGPL-3.0-only
& GPL-3.0-only & LGPL-2.0-only & BSD-2-Clause & BSD-3-Clause & TCL &
Apache-2.0-with-LLVM-exception"
meta/recipes-devtools/autoconf-archive/autoconf-archive_2024.10.16.bb:LICENS
E = "GPL-3.0-with-autoconf-exception"
meta/recipes-devtools/gcc/gcc-14.2.inc:LICENSE = "GPL-3.0-with-GCC-exception
& GPL-3.0-only"
meta/recipes-devtools/gcc/gcc-runtime.inc:LICENSE =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgcc-initial.inc:LICENSE =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgcc.inc:LICENSE:${PN} =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgcc.inc:LICENSE:${PN}-dev =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgcc.inc:LICENSE:${PN}-dbg =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgfortran.inc:LICENSE:${PN} =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgfortran.inc:LICENSE:${PN}-dev =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gcc/libgfortran.inc:LICENSE:${PN}-dbg =
"GPL-3.0-with-GCC-exception"
meta/recipes-devtools/gnu-config/gnu-config_git.bb:LICENSE =
"GPL-3.0-with-autoconf-exception"
meta/recipes-devtools/llvm/llvm_19.1.3.bb:LICENSE =
"Apache-2.0-with-LLVM-exception"
meta/recipes-devtools/rust/rust-llvm_1.80.1.bb:LICENSE ?=
"Apache-2.0-with-LLVM-exception"
meta/recipes-extended/xz/xz_5.6.3.bb:LICENSE = "GPL-2.0-or-later &
GPL-3.0-with-autoconf-exception & LGPL-2.1-or-later & 0BSD"
meta/recipes-graphics/glslang/glslang_1.3.296.0.bb:LICENSE = "BSD-3-Clause &
BSD-2-Clause & MIT & Apache-2.0 & GPL-3-with-bison-exception"
meta/recipes-support/libgit2/libgit2_1.8.2.bb:LICENSE =
"GPL-2.0-with-GCC-exception & MIT & OpenSSL & BSD-3-Clause & Zlib & ISC &
LGPL-2.1-or-later & CC0-1.0 & BSD-2-Clause"

To migrate Apache-2.0-with-LLVM-exception to Apache-2.0 WITH LLVM-exception
should be straight forward. [^1]
GPL-3.0-with-GCC-exception becomes "WITH GCC-exception-3.1", but we have to
check if it is GPL-3.0-only or GPL-3.0-or-later first. [^2]
GPL-3.0-with-autoconf-exception becomes "WITH Autoconf-exception-3.0" and
also the check first. [^3]
GPL-2.0-with-bison-exception becomes "WITH Bison-exception-2.2" and also the
check first. [^4]

This is from a SPDX point of view.
If the source explicitly states the deprecated license, it could be better
to stay with that one.

[^1]: https://spdx.org/licenses/LLVM-exception.html
[^2]: https://spdx.org/licenses/GPL-3.0-with-GCC-exception.html
[^3]: https://spdx.org/licenses/GPL-3.0-with-autoconf-exception.html
[^4]: https://spdx.org/licenses/GPL-2.0-with-bison-exception.html

-----Original Message-----
From: Alexander Kanavin <[email protected]> 
Sent: Monday, November 25, 2024 12:59 PM
To: Denis OSTERLAND-HEIM <[email protected]>
Cc: [email protected]
Subject: [EXT] Re: [OE-core] [PATCH 3/3] linux-yocto: add WITH
Linux-syscall-note to LICENSE

[EXTERNAL EMAIL]
 

Thanks, the patchset is fine, but I wonder if there are other recipes in
oe-core which would benefit from WITH suppport?

Alex

On Mon, 25 Nov 2024 at 12:58, Denis OSTERLAND-HEIM via
lists.openembedded.org <[email protected]>
wrote:
>
> According to Linux COPYING file this exception is made to GPL v2.
>
> Signed-off-by: Denis Osterland-Heim <[email protected]>
> ---
>  meta/files/common-licenses/Linux-syscall-note | 25 +++++++++++++++++++
>  meta/recipes-kernel/linux/linux-yocto.inc     |  2 +-
>  2 files changed, 26 insertions(+), 1 deletion(-)  create mode 100644 
> meta/files/common-licenses/Linux-syscall-note
>
> diff --git a/meta/files/common-licenses/Linux-syscall-note
> b/meta/files/common-licenses/Linux-syscall-note
> new file mode 100644
> index 0000000000..9abdad71fa
> --- /dev/null
> +++ b/meta/files/common-licenses/Linux-syscall-note
> @@ -0,0 +1,25 @@
> +SPDX-Exception-Identifier: Linux-syscall-note
> +SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
> +SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, 
> +LGPL-2.1,
> LGPL-2.1+, GPL-2.0-only, GPL-2.0-or-later
> +Usage-Guide:
> +  This exception is used together with one of the above SPDX-Licenses
> +  to mark user space API (uapi) header files so they can be included
> +  into non GPL compliant user space application code.
> +  To use this exception add it with the keyword WITH to one of the
> +  identifiers in the SPDX-Licenses tag:
> +    SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
> +License-Text:
> +
> +   NOTE! This copyright does *not* cover user programs that use 
> + kernel services by normal system calls - this is merely considered 
> + normal use of the kernel, and does *not* fall under the heading of
"derived work".
> + Also note that the GPL below is copyrighted by the Free Software 
> + Foundation, but the instance of code that it refers to (the Linux
> + kernel) is copyrighted by me and others who actually wrote it.
> +
> + Also note that the only valid version of the GPL as far as the 
> + kernel is concerned is _this_ particular version of the license (ie 
> + v2, not
> + v2.2 or v3.x or whatever), unless explicitly otherwise stated.
> +
> +                       Linus Torvalds
> +
> diff --git a/meta/recipes-kernel/linux/linux-yocto.inc
> b/meta/recipes-kernel/linux/linux-yocto.inc
> index 0132fcffb3..3de8318c39 100644
> --- a/meta/recipes-kernel/linux/linux-yocto.inc
> +++ b/meta/recipes-kernel/linux/linux-yocto.inc
> @@ -1,6 +1,6 @@
>  SUMMARY = "Linux kernel"
>  SECTION = "kernel"
> -LICENSE = "GPL-2.0-only"
> +LICENSE = "GPL-2.0-only + Linux-syscall-note"
>  HOMEPAGE = "https://www.yoctoproject.org/";
>
>  LIC_FILES_CHKSUM ?= "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> --
> 2.45.2
>
> 
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#207786): 
https://lists.openembedded.org/g/openembedded-core/message/207786
Mute This Topic: https://lists.openembedded.org/mt/109769586/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to