From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 40579@debbugs.gnu.org
Subject: [bug#40579] [RFC PATCH] add iPXE.
Date: Sun, 12 Apr 2020 23:18:21 +0200 [thread overview]
Message-ID: <87tv1ommhu.fsf@nckx> (raw)
In-Reply-To: <20200412214609.57f92dcc@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]
Hullo Danny,
Danny Milosavljevic 写道:
> Tobias Geerinckx-Rice via Guix-patches via
> <guix-patches@gnu.org> wrote:
>
>> Could you elaborate? What's "interesting" about it? That all
>> looks very boring and straightforward to me (which is good! :-)
>> —
>> the result is GPL2-only, no?
>
> No, there are different makefile targets (rom output filenames)
> which will
> result in different parts of ipxe to be built and included in
> the output.
>
> There's special makefile targets for each of these targets to
> determine
> the license that applies to each of the latter targets,
> respectively.
OK. This was already clear.
I'm now convinced that this whole make target thing is a
misunderstanding and a distraction: iPXE licencing is not, in any
way, ‘generated on the fly by make rules’ or ‘unclear’ or
‘interesting’. It's boring. It's good. It's GPL2.
λ grep -hr '^FILE_LICENCE ( .* );' * | sort -u
FILE_LICENCE ( BSD2 );
FILE_LICENCE ( BSD3 );
FILE_LICENCE ( GPL2_ONLY );
FILE_LICENCE ( GPL2_OR_LATER );
FILE_LICENCE ( GPL2_OR_LATER_OR_UBDL );
FILE_LICENCE ( GPL_ANY );
FILE_LICENCE ( MIT );
FILE_LICENCE ( PUBLIC_DOMAIN );
Just a normal Free software package. Happens to bundle a Perl
script similar to <https://linux.die.net/man/1/licensecheck> (but
less useful). Nothing to see here.
> Did you try to make all of the targets' license targets?
No. I hope I've shown they're irrelevant now.
What is relevant is that some files are missing licence headers
(e.g. drivers/net/tg3/tg3_phy.c). However, this is so common as
to be standard (Guix wouldn't exist if we demanded headers in
every file) and COPYING says that these are licenced under ‘the
GPL’. That's… acceptable.
> P.S. The following ROMs are not reproducible:
>
> 10222000.rom GPL2
> 10500940.rom GPL2
> 10ec8139.rom GPL2
> 15ad07b0.rom GPL2+
> 1af41000.rom GPL2+
> 8086100e.mrom GPL2+
> 8086100f.mrom GPL2+
> 808610d3.mrom GPL2+
> 80861209.rom GPL2+
> ipxe.iso license checker doesn't work
> rtl8139.rom GPL2
Ooh, thanks for catching that.
I noticed that Debian installs a very different set of file(
name)s[0] than we do. I don't know what that means though.
Kind regards,
T G-R
[0]: https://packages.debian.org/sid/all/ipxe/filelist
https://packages.debian.org/sid/all/ipxe-qemu/filelist
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-12 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 17:59 [bug#40579] [RFC PATCH] add iPXE Vincent Legoll
2020-04-12 18:47 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-12 18:58 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-12 19:46 ` Danny Milosavljevic
2020-04-12 21:18 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-04-12 23:28 ` [bug#40579] [PATCH v2] gnu: Add iPXE Tobias Geerinckx-Rice via Guix-patches via
2020-04-14 15:11 ` [bug#40579] [PATCH v3] " Vincent Legoll
2020-04-15 20:41 ` [bug#40579] [PATCH v2] " Danny Milosavljevic
2020-04-15 20:55 ` Vincent Legoll
2020-06-09 19:31 ` Brice Waegeneire
2020-06-09 19:58 ` Vincent Legoll
2020-06-09 20:11 ` Brice Waegeneire
2021-01-12 21:01 ` Vincent Legoll
2021-01-12 21:44 ` [bug#40579] [PATCH 1/2] " Vincent Legoll
2021-01-12 21:44 ` [bug#40579] [PATCH 2/2] gnu: ipxe: Update to 1.21.1 Vincent Legoll
2021-01-12 21:47 ` [bug#40579] [PATCH 1/2] gnu: Add iPXE Vincent Legoll
2021-01-14 0:53 ` Danny Milosavljevic
2021-01-14 8:33 ` bug#40579: [RFC PATCH] add iPXE Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv1ommhu.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=40579@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=me@tobias.gr \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).