Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/6] package/gnu-efi: fix legal-info
Date: Sun, 5 Apr 2015 19:31:34 +0200	[thread overview]
Message-ID: <20150405173134.GE4134@free.fr> (raw)
In-Reply-To: <20150405191745.3497f9a7@free-electrons.com>

Thomas, All,

On 2015-04-05 19:17 +0200, Thomas Petazzoni spake thusly:
> On Sun,  5 Apr 2015 18:48:26 +0200, Yann E. MORIN wrote:
> > Fix a bunch of deficiencies:
> >   - 'debian/copyright' does not exist.
> >   - gnuefi is not GPLv2+. Only one AArch64 file has GPLv2+ headers,
> >     all others have BSD-3c
> >   - efilib is BSD-2c
> 
> I don't quite agree here: some ARM files are also under GPLv2+, so I
> believe the whole thing really is under GPLv2+.

The reasoning for changing that is:
  - there are two files with a GPLv2+ header;
    - gnuefi/crt0-efi-aarch64.S -> GPLv2+ or something like a BSD-2c
    - gnuefi/crt0-efi-arm.S     -> GPLv2+
  - all other files are BSD-3c (or have no licensing info)
  - we don't build gnuefi for ARM or AArch64, only for x86 or x86_64

However, re-reading README.gnuefi, we can read this:

---8<---
 gnuefi: This directory contains the glue necessary to convert ELF64
        binaries to EFI binaries.  Various runtime code bits, such as
        a self-relocator are included as well.  This code has been
        contributed by the Hewlett-Packard Company and is distributed
        under the GNU GPL.
---8<---

This is very confusing.Waht about changing to:

GNU_EFI_LICENSE = BSD-3c and/or GPLv2+ (gnuefi), BSD-3c (efilib)

> This is also apparently the opinion of Debian:
> http://changelogs.ubuntu.com/changelogs/pool/main/g/gnu-efi/gnu-efi_3.0i-2ubuntu1/copyright.

Well, I mostly disagree there, if only by looking at the files we *do*
build (others we don't care).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-04-05 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 16:48 [Buildroot] [PATCH 0/6] legal-info: fix packages (branch yem/legal) Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 1/6] package/liblinear: fix legal-info Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 2/6] package/python-cherrypy: " Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 3/6] package/zmqpp: " Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 4/6] package/evemu: " Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 5/6] package/gnu-efi: " Yann E. MORIN
2015-04-05 17:17   ` Thomas Petazzoni
2015-04-05 17:31     ` Yann E. MORIN [this message]
2015-04-05 17:36       ` Thomas Petazzoni
2015-04-05 17:40         ` Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 6/6] package/linux-firmware: " Yann E. MORIN
2015-04-05 17:17 ` [Buildroot] [PATCH 0/6] legal-info: fix packages (branch yem/legal) Thomas Petazzoni

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=20150405173134.GE4134@free.fr \
    --to=yann.morin.1998@free.fr \
    --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