all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 46703@debbugs.gnu.org
Cc: qblade@protonmail.com
Subject: [bug#46703] [PATCH] gnu: add bmake
Date: Sat, 27 Feb 2021 15:15:25 +0100	[thread overview]
Message-ID: <87k0qt1ts2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <E7Qpz20wDnxkH9EMr_sSqYVJxFll3zNTfHV4CwBtwTUprV_zfwhfo8o9faxuShmQxAGcTws9kKae8RtsQkPhnlH9DY5I8oep5T1LTaq4LWs=@protonmail.com> (qblade via Guix-patches via's message of "Mon, 22 Feb 2021 06:33:57 +0000")

Hello,

qblade via Guix-patches via <guix-patches@gnu.org> writes:

> * gnu/packages/build-tools.scm (bmake): New variable.

Thank you. Some comments follow.

> +    (name "bmake")
> +    (version "20200902")

There is a newer version available. Could you provide it instead?

I tried to quickly update it (hash
"07n9avzdg6gifrzyddnyzada5s5rzklvbqfpv5drljpxcgpqpvwg") but there are
additional failing tests.

> +    (arguments
> +     `(#:tests? #f ;; test in build

You need a single semicolon for end-of-line comments. Also (nitpick),
I find ";test during build" clearer.

> +       #:phases
> +       (modify-phases %standard-phases
> +         (add-after 'configure 'fix-test ;; fix from nixpkgs

See above for comment syntax.

> +    (description "Program designed to simplify the maintenance of
> +other programs.")

I suggest:

    "bmake is a program designed to simplify the maintenance of other
    programs.  Its input is a list of specifications as to the files upon which
    programs and other files depend."

Could you send an updated patch?

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2021-02-27 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  6:33 [bug#46703] [PATCH] gnu: add bmake qblade via Guix-patches via
2021-02-27 14:15 ` Nicolas Goaziou [this message]
2021-02-28  4:27   ` [bug#46703] 回复: " qblade via Guix-patches via
2021-03-02 10:58     ` Nicolas Goaziou

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=87k0qt1ts2.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=46703@debbugs.gnu.org \
    --cc=qblade@protonmail.com \
    /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.