From: Danny Milosavljevic <dannym@scratchpost.org>
To: Nam Nguyen <namn@berkeley.edu>
Cc: 33756@debbugs.gnu.org
Subject: [bug#33756] correction
Date: Sun, 16 Dec 2018 12:55:12 +0100 [thread overview]
Message-ID: <20181216125512.132a3e41@scratchpost.org> (raw)
In-Reply-To: <20181215164915.GA1300@antelope>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi,
thanks for the patch. I have the following suggestions:
* It's easier to just use #:make-flags to override the CC make variable -- and
it doesn't require a custom phase
* It's clearer to use #:tests? #f to indicate that there are no tests.
* install-file makes sure that the destination directory exists already,
so it's useless to manually create it
* sctd.sh uses "which" to find the "sct" executable. Please patch it
so that it uses the sct executable of (assoc-ref outputs "out") "/bin"
(i.e. hard-code it) instead
* sctd.sh uses "logger" which is part of inetutils, so inetutils should
be a regular input. Moreover, please patch sctd.sh so it uses inetutils'
logger (i.e. hard-code it using (assoc-ref inputs "inetutils"))
* sctd.sh uses "date", "printf" and "sleep" which are part of coreutils,
so coreutils should be a regular input. Moreover, please patch sctd.sh so
it uses coreutils' things (i.e. hard-code it using (assoc-ref inputs "coreutils")
(See other files for how to use "substitute*" to patch things)
Could you send an updated patch?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-16 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 7:09 [bug#33756] [PATCH] gnu: Add sct Nam Nguyen
2018-12-15 16:49 ` [bug#33756] correction Nam Nguyen
2018-12-16 11:55 ` Danny Milosavljevic [this message]
2018-12-16 21:25 ` [bug#33756] [PATCH] gnu: Add sct Nam Nguyen
2018-12-23 17:37 ` bug#33756: " Ludovic Courtès
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=20181216125512.132a3e41@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=33756@debbugs.gnu.org \
--cc=namn@berkeley.edu \
/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.