From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 40579@debbugs.gnu.org
Subject: [bug#40579] [RFC PATCH] add iPXE.
Date: Sun, 12 Apr 2020 20:47:23 +0200 [thread overview]
Message-ID: <87y2r0mthg.fsf@nckx> (raw)
In-Reply-To: <e7f84fcc-a555-4ef8-2f6b-1bf31a9496a7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3229 bytes --]
Vincent,
Thank you! Brief review, will build & maybe notice more later:
Vincent Legoll 写道:
> The licensing is "interesting", see:
>
> https://ipxe.org/licensing
>
> Is that a problem ?
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?
+ (file-name (string-append name "-" version
"-checkout"))
You can use the GIT-FILE-NAME helper here.
+ `(#:phases (modify-phases %standard-phases
Aside: I'd indent arguments' #:keywords as
+ `(#:phases
+ (modify-phases %standard-phases
to give you more breathing room at deeper indentation levels.
It's
not needed now, but if someone were to add a new phase they might
have
to
do
annoying
things,
or re-indent the entire thing later, causing noise. Maybe that's
just me though.
+ (add-after 'unpack 'add-real-make-install
+ (lambda* (#:key outputs #:allow-other-keys)
+ (substitute* "src/Makefile"
+ (("^install :")
+ (string-append "install :"
+ "\n\t@$(MKDIR) -p "
+ (assoc-ref outputs "out")
"/bin"
+ "\n\t@$(CP) $(ALL) "
+ (assoc-ref outputs "out")
"/bin"
+ "\n\n__old_install :")))
Interesting approach! I'm OK with it; looking at ALL it wouldn't
be more readable or future-proff to use FIND-FILES & Scheme.
/bin is not the right place for these files. /lib/ipxe looks to
be the standard; let's use that.
+ (replace 'build
+ (lambda _ (with-directory-excursion "src"
+ (invoke "make" "-j"
(number->string
+
(parallel-job-count))))))
Let's, instead:
(add-after 'unpack 'enter-source-directory
(lambda _ (chdir "src") #t))
Don't worry, the state can't hurt you now. Now we can keep the
standard build & install phases.
It might be necessary to add a ‘leave-source-directory’ after
'install to make sure the licence files are still installed to
share/doc/.
+ #:tests? #f))
→ #:tests? #f)) ; no test suite
+ (native-inputs
Nitpick: sort? :-)
+ (synopsis "PXE-compliant network boot firmware")
I personally like the ‘these are just boot loaders’ angle, but
would users expect to find this in (gnu packages firmware)
instead? Shrug.
+ (license license:gpl2+)))
‘gpl2’ as mentioned above.
If you feel like it (there aren't that many files) you could list
the licences for each output binary, but that's optional. The
combined work appears to be GPL2.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-12 18:48 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2r0mthg.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=40579@debbugs.gnu.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 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.