From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 34175@debbugs.gnu.org
Subject: [bug#34175] [PATCH 1/4] gnu: Add gnu-efi.
Date: Fri, 25 Jan 2019 18:48:24 +0100 [thread overview]
Message-ID: <20190125184824.52fb680e@scratchpost.org> (raw)
In-Reply-To: <87sgxj7q8u.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]
Hi,
On Wed, 23 Jan 2019 09:05:53 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:
> Hi Danny,
>
> > * gnu/packages/efi.scm: New file.
> > * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
> […]
> > diff --git a/gnu/packages/efi.scm b/gnu/packages/efi.scm
> > new file mode 100644
> > index 000000000..3a92370ef
> > --- /dev/null
> > +++ b/gnu/packages/efi.scm
> > @@ -0,0 +1,52 @@
> > +;;; GNU Guix --- Functional package management for GNU
> > +;;; Copyright © 2016 Danny Milosavljevic <dannym@scratchpost.org>
>
> It’s 2019.
Ah, it must be a new low of me getting the year wrong ;-)
> > + ;; FIXME: https://metadata.ftp-master.debian.org/changelogs/main/g/gnu-efi/gnu-efi_3.0.9-1_copyright
> > + (license license:gpl2)))
>
> What does the FIXME tell us to do? Should this be
>
> ;; The code can be distributed under the terms of either license
> (license (list license:gpl2+ license:expat))
I wanted the reuse the work Debian already did. They list:
* BSD-3-clause-HP
* BSD-2-clause-Linaro or gpl-2+
* BSD-2-clause-Intel
* Expat
* BSD-4-clause-Intel
* GPL-2+
BSD-4-clause is incompatible with GPL.
Therefore, it's lucky that they say "BSD-2-clause-Linaro OR gpl-2+", otherwise
we could not have distributed gnu-efi.
So I suggest:
;; Distribution is allowed only when accepting all those licenses.
(license (list license:bsd-2 license:bsd-3 license:bsd-4 license:expat))
What do you think?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-25 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 0:00 [bug#34175] [PATCH 0/4] Add EFI tools Danny Milosavljevic
2019-01-23 0:03 ` [bug#34175] [PATCH 1/4] gnu: Add gnu-efi Danny Milosavljevic
2019-01-23 0:03 ` [bug#34175] [PATCH 2/4] gnu: Add sbsigntools Danny Milosavljevic
2019-01-23 8:08 ` Ricardo Wurmus
2019-01-23 14:09 ` Danny Milosavljevic
2019-01-23 0:03 ` [bug#34175] [PATCH 3/4] gnu: Add efitools Danny Milosavljevic
2019-01-23 8:09 ` Ricardo Wurmus
2019-01-23 0:03 ` [bug#34175] [PATCH 4/4] gnu: Add efilinux Danny Milosavljevic
2019-01-23 8:12 ` Ricardo Wurmus
2019-01-23 8:05 ` [bug#34175] [PATCH 1/4] gnu: Add gnu-efi Ricardo Wurmus
2019-01-25 17:48 ` Danny Milosavljevic [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=20190125184824.52fb680e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=34175@debbugs.gnu.org \
--cc=rekado@elephly.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.