From: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
To: Rasmus Villemoes <ravi@prevas.dk>, Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Ross Burton <Ross.Burton@arm.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: RE: [EXT] Re: [OE-core] [PATCH v2] linux-yocto: add and use GPL-2.0-with-syscall-note license
Date: Wed, 4 Dec 2024 10:06:04 +0100 (CET) [thread overview]
Message-ID: <bf5528fee82e4383ab659c8d944943fb@diehl.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]
Hi,
Currently I wonder if common-licenses is the right place for Linux-syscall-note,
because this is a Linux specific licenses.
I agree with Ross that SPDX syntax for the LICENSE field would be the best.
First step:
LICENSE = "GPL-2.0-only & Linux-syscall-note"
NO_GENERIC_LICENSE[Linux-syscall-note] = "file://LICENSES/exceptions/Linux-syscall-note"
And with SPDX syntax:
LICENSE = "GPL-2.0-only WITH Linux-syscall-note"
Maybe in the future we can even use https://github.com/spdx/license-list-data
instead of maintaining common-licenses on our own.
Regards, Denis
-----Original Message-----
From: Rasmus Villemoes <ravi@prevas.dk>
Sent: Tuesday, December 3, 2024 2:18 PM
To: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [EXT] Re: [OE-core] [PATCH v2] linux-yocto: add and use GPL-2.0-with-syscall-note license
> So since you're combining thbe GPL text and the syscall-note text, why
> not take an exact copy of the COPYING file as it existed in the kernel
> tree before the current split. That would also make word "below" actually make
> sense. I.e.,
>
> git show b3358a116:COPYING
>
> Rasmus
-----Original Message-----
From: Khem Raj <raj.khem@gmail.com>
Sent: Tuesday, December 3, 2024 6:38 PM
To: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [EXT] Re: [OE-core] [PATCH v2] linux-yocto: add and use GPL-2.0-with-syscall-note license
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/LICENSES/exceptions/Linux-syscall-note
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/LICENSES/preferred/GPL-2.0
>
> I know we have combined the exceptions and create individual files but
> I wonder if there is a better way to
> express it with combinations of files. eg. see
> meta/files/common-licenses/GPL-3.0-with-GCC-exception
> at the top it says "insert GPL v3 text here" seems a bit iffy. Instead
> it could be expressed with two files having
> full license texts.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3908 bytes --]
reply other threads:[~2024-12-04 9:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bf5528fee82e4383ab659c8d944943fb@diehl.com \
--to=denis.osterland@diehl.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=raj.khem@gmail.com \
--cc=ravi@prevas.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.