($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: rybczynska@gmail.com
Cc: nikhilar2410@gmail.com,
	OE-core <openembedded-core@lists.openembedded.org>,
	 Bhabu Bindu <bhabu.bindu@kpit.com>, Nikhil R <nikhil.r@kpit.com>,
	 Bhabu Bindu <bindudaniel1996@gmail.com>
Subject: Re: [OE-core][kirkstone][PATCH] xz: Update LICENSE variable for xz packages
Date: Tue, 7 May 2024 09:23:16 -0700	[thread overview]
Message-ID: <CAMKF1sp+htWDnwfzv26+s=7gmHORW5Ux320j=AMyzWxjvi4BcA@mail.gmail.com> (raw)
In-Reply-To: <CAApg2=TB81yXyxpt8kEaoHB-SCoJ8753w77FWby2m8Qj-nDEig@mail.gmail.com>

On Mon, May 6, 2024 at 8:33 AM Marta Rybczynska via
lists.openembedded.org <rybczynska=gmail.com@lists.openembedded.org>
wrote:
>
>
>
> On Mon, 6 May 2024, 13:09 nikhil via lists.openembedded.org, <nikhilar2410=gmail.com@lists.openembedded.org> wrote:
>>
>> Update LICENSE defined for xz packages to match the license
>> information provided in the xz COPYING file.
>>
>> The License information from PACKAGERS file of xz mentions
>> packages with lzma files are in public domain.They ask to
>> use GPLv2+, if only it's not possible to mention "PD and GPLv2+".
>>
>> Include PD license with GPLv2 to packages with lzma content:
>> xz-dev package contains lzma header
>> xz-doc package contains lzma man pages
>> xz packages contains lzma binaries
>>
>> Links: https://github.com/tukaani-project/xz/blob/v5.2.6/COPYING
>>        https://github.com/tukaani-project/xz/blob/v5.4.1/PACKAGERS
>>
>> Signed-off-by: Bhabu Bindu <bindudaniel1996@gmail.com>
>> ---
>>  meta/recipes-extended/xz/xz_5.2.6.bb | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/recipes-extended/xz/xz_5.2.6.bb b/meta/recipes-extended/xz/xz_5.2.6.bb
>> index 3482622471..33496748bc 100644
>> --- a/meta/recipes-extended/xz/xz_5.2.6.bb
>> +++ b/meta/recipes-extended/xz/xz_5.2.6.bb
>> @@ -9,10 +9,10 @@ SECTION = "base"
>>  # libgnu, which appears to be used for DOS builds. So we're left with
>>  # GPL-2.0-or-later and PD.
>>  LICENSE = "GPL-2.0-or-later & GPL-3.0-with-autoconf-exception & LGPL-2.1-or-later & PD"
>> -LICENSE:${PN} = "GPL-2.0-or-later"
>> -LICENSE:${PN}-dev = "GPL-2.0-or-later"
>> +LICENSE:${PN} = "PD & GPL-2.0-or-later"
>> +LICENSE:${PN}-dev = "PD & GPL-2.0-or-later"
>>  LICENSE:${PN}-staticdev = "GPL-2.0-or-later"
>> -LICENSE:${PN}-doc = "GPL-2.0-or-later"
>> +LICENSE:${PN}-doc = "PD & GPL-2.0-or-later"
>>  LICENSE:${PN}-dbg = "GPL-2.0-or-later"
>>  LICENSE:${PN}-locale = "GPL-2.0-or-later"
>>  LICENSE:liblzma = "PD"
>> --
>> 2.25.1
>
>
> I'm not a copyright lawyer, but from what I understand public domain is not a licence. For a discussion see https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
>

rather each PD is a license of its own is what I understand.

> The next version of xz will be 0BSD so the statement will change too.
>
> Regards,
> Marta
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#199047): https://lists.openembedded.org/g/openembedded-core/message/199047
> Mute This Topic: https://lists.openembedded.org/mt/105937026/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


      parent reply	other threads:[~2024-05-07 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 11:08 [OE-core][kirkstone][PATCH] xz: Update LICENSE variable for xz packages Nikhil R
2024-05-06 15:32 ` Marta Rybczynska
2024-05-07 10:02   ` Alexander Kanavin
2024-05-07 16:23   ` Khem Raj [this message]

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='CAMKF1sp+htWDnwfzv26+s=7gmHORW5Ux320j=AMyzWxjvi4BcA@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=bhabu.bindu@kpit.com \
    --cc=bindudaniel1996@gmail.com \
    --cc=nikhil.r@kpit.com \
    --cc=nikhilar2410@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rybczynska@gmail.com \
    /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).