unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Josh Holland <josh@inv.alid.pw>
Cc: 35653@debbugs.gnu.org
Subject: [bug#35653] [PATCH] gnu: Add rcm.
Date: Thu, 9 May 2019 18:52:56 +0200	[thread overview]
Message-ID: <20190509185256.309d9b63@scratchpost.org> (raw)
In-Reply-To: <20190509153834.26585-1-josh@inv.alid.pw>

[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]

Hi,

On Thu,  9 May 2019 16:38:34 +0100
Josh Holland <josh@inv.alid.pw> wrote:

> First, I wasn't sure whether it fits into an existing module already.
> I had a look through the contents of gnu/packages/ but I didn't see
> anything that really stuck out.  Perhaps it fits into shellutils?

Yes, and it's not so important in which module what is.  The module
name is not part of the package name anyway, so we are mostly using
it to manage compilation complexity (sigh).  Developers can find it
using "guix edit rcm" anyway.

I try not to introduce a new module for each package because it leads
to a lot of file header duplication, and at some point the comment/code
ratio is getting ridiculous--but, technically, even that would be fine.

> This may or may not be the right way to go about things; I'd appreciate
> some feedback on that.

Looks fine.

> If there are any ideas to solve the tests, or any other issues that need
> fixing, I'm happy to re-submit the patch.

> +    (arguments '(#:tests? #f))

From your description, try (#:parallel-tests? #f) instead of (#:tests? #f).

Nice work!

Some test scripts still have /bin/sh

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-05-09 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 15:38 [bug#35653] [PATCH] gnu: Add rcm Josh Holland
2019-05-09 16:52 ` Danny Milosavljevic [this message]
2019-05-09 17:59   ` Josh Holland
2019-05-09 17:59     ` [bug#35653] [PATCH v2] " Josh Holland
2019-12-10  6:55       ` Brett Gilio
2020-01-15 21:42       ` bug#35653: " Ludovic Courtès
2020-01-02 15:11 ` [bug#35653] " Jakub Kądziołka

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=20190509185256.309d9b63@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=35653@debbugs.gnu.org \
    --cc=josh@inv.alid.pw \
    /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).