From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/joe: license is GPL-2.0+
Date: Fri, 20 Sep 2019 13:49:07 +0200 [thread overview]
Message-ID: <20190920134907.57655470@windsurf> (raw)
In-Reply-To: <CAGm1_kvyftWG87WG-Vn4whgi2jw=amS0PZoC5GHRUtV5-xQ+wg@mail.gmail.com>
On Fri, 20 Sep 2019 13:36:48 +0200
Yegor Yefremov <yegorslists@googlemail.com> wrote:
> Hi Peter,
>
> On Fri, Sep 20, 2019 at 1:30 PM Peter Korsgaard <peter@korsgaard.com> wrote:
> >
> > Joe changed the COPYING file from GPL-1.0 to GPL-2.0 in the development
> > leading up to 3.8:
> >
> > https://sourceforge.net/p/joe-editor/mercurial/ci/d731f9b3794bc4c896f2efa1c97ac2c82c3365ac/
> >
> > So change the license to GPL-2.0+
>
> GPL-2.0+, GPL-2.0 etc. identifiers are deprecated [1].
I was aware of GPL-2.0+ being deprecated, but not GPL-2.0. And indeed
SPDX now uses GPL-2.0-or-later (instead of GPL-2.0+) and GPL-2.0-only
(instead of GPL-2.0).
> What should we do? Should we switch to the new ones?
Ideally yes, to follow SPDX. However, there are a few gotchas:
- The number of packages that need to be changed (though that's easily
doable with sed)
- The potential backward compatibility breakage. If people have
scripts/tools that parses our manifest.csv and interpret the license
values, the renaming might break for them.
But maybe these are not that important, and sticking to SPDX is mort
important ?
Anyway, that's a separate discussion from Peter's patch. Peter's patch
is fine as-is, as it matches the current practice in Buildroot.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-20 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 11:30 [Buildroot] [PATCH] package/joe: license is GPL-2.0+ Peter Korsgaard
2019-09-20 11:36 ` Yegor Yefremov
2019-09-20 11:49 ` Thomas Petazzoni [this message]
2019-09-20 11:56 ` Peter Korsgaard
2019-09-20 12:19 ` Thomas Petazzoni
2019-09-21 13:53 ` Arnout Vandecappelle
2019-09-30 13:51 ` Peter Korsgaard
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=20190920134907.57655470@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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