From: <Mikko.Rapeli@bmw.de>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] elfutils: update LICENSE to include GPLv2 for shared libraries
Date: Thu, 11 Apr 2019 11:02:00 +0000 [thread overview]
Message-ID: <20190411110200.GG20077@hiutale> (raw)
In-Reply-To: <20190411104042.GE20077@hiutale>
On Thu, Apr 11, 2019 at 10:40:43AM +0000, openembedded-core-bounces@lists.openembedded.org wrote:
> On Thu, Apr 11, 2019 at 12:48:40PM +0300, Mikko Rapeli wrote:
> > NEWS file in the sources says this about switch from GPLv2 to
> > GPLv3 license:
> >
> > https://sourceware.org/git/?p=elfutils.git;a=blob;f=NEWS;h=5a06047f255e3c9a63828953759fd18a4ba9a3f3;hb=HEAD#l362
> >
> > 362 The license is now GPLv2/LGPLv3+ for the libraries and GPLv3+ for stand-alone
> > 363 programs. There is now also a formal CONTRIBUTING document describing how to
> > 364 submit patches.
> >
> > libasm, libdw and libelf are thus covered optionally by GPLv2 license.
> >
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
> > ---
> > meta/recipes-devtools/elfutils/elfutils_0.175.bb | 14 +++++++++++++-
> > 1 file changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-devtools/elfutils/elfutils_0.175.bb b/meta/recipes-devtools/elfutils/elfutils_0.175.bb
> > index b0b9ddc..6d1279a 100644
> > --- a/meta/recipes-devtools/elfutils/elfutils_0.175.bb
> > +++ b/meta/recipes-devtools/elfutils/elfutils_0.175.bb
> > @@ -1,7 +1,7 @@
> > SUMMARY = "Utilities and libraries for handling compiled object files"
> > HOMEPAGE = "https://sourceware.org/elfutils"
> > SECTION = "base"
> > -LICENSE = "(GPLv3 & Elfutils-Exception)"
> > +LICENSE = "(GPLv2 & LGPLv3+ & GPLv3+ & Elfutils-Exception)"
>
> Can anyone find the Elfutils-Exception in current 0.175 or sumo 0.170 sources?
>
> Debian is also listing libraries with GPLv2+ | LGPLv3+ and executables
> with GPLv3+ in
>
> https://tracker.debian.org/media/packages/e/elfutils/copyright-0.176-1
>
> Should I also drop the Elfutils-Exception?
I will send a new version which drops Elfutils-Exception since it no longer
exists after tag elfutils-0.154 and commit:
commit de2ed97f33139af5c7a0811e4ec66fc896a13cf2
Author: Mark Wielaard <mjw@redhat.com>
Date: Tue Jun 5 17:15:16 2012 +0200
Update name, license and contributor policy.
* Change name from "Red Hat elfutils" to "elfutils".
* Update license of standalone tools and test from GPLv2 to GPLv3+.
* Change license of libraries from GPLv2+exception to GPLv2/LGPLv3+.
* Add Developer Certificate of Origin based contributor policy.
top-level:
- COPYING: Upgraded from GPLv2 to GPLv3.
- CONTRIBUTING, COPYING-GPLv2, COPYING-LGPLv3: New files.
- NEWS: Added note about new contribution and license policy.
- Makefile.am: Updated to GPLv3, added new files to EXTRA_DIST.
- configure.ac: Update to GPLv3, changed AC_INIT name to 'elfutils'.
backends, lib, libasm, libcpu, libdw, libdwfl, libebl, libelf:
- All files updated to GPLv2/LGPLv3+. Except some very small files
(<5 lines) which didn't have any headers at all before, the linker
.maps files and the libcpu/defs files which only contain data and
libelf/elf.h which comes from glibc and is under LGPLv2+.
config:
- elfutils.spec.in: Add new License: headers and new %doc files.
- Update all license headers to GPLv2/LGPLv3+ for files used by libs.
src, tests:
- All files updated to GPLv3+. Except for the test bz2 data files, the
linker maps and script files and some very small files (<5 lines)
that don't have any headers.
Signed-off-by: Richard Fontana <rfontana@redhat.com>
Signed-off-by: Mark Wielaard <mjw@redhat.com>
-Mikko
prev parent reply other threads:[~2019-04-11 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 9:48 [PATCH] elfutils: update LICENSE to include GPLv2 for shared libraries Mikko Rapeli
2019-04-11 10:40 ` Mikko.Rapeli
2019-04-11 11:02 ` Mikko.Rapeli [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=20190411110200.GG20077@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.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