[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: branch master updated: services: cuirass: Add a no-publish argument.
From: |
Ludovic Courtès |
Subject: |
Re: branch master updated: services: cuirass: Add a no-publish argument. |
Date: |
Thu, 12 Aug 2021 23:22:53 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Hi!
guix-commits@gnu.org skribis:
> commit d128c6fd33f46ec4e2d0ef352d20a858c377bf6f
> Author: Mathieu Othacehe <othacehe@gnu.org>
> AuthorDate: Thu Aug 12 12:58:34 2021 +0200
>
> services: cuirass: Add a no-publish argument.
>
> * gnu/services/cuirass.scm (<cuirass-remote-server-configuration>): Add a
> no-publish? field.
> (cuirass-shepherd-service): Honor it.
> * doc/guix.texi (Cuirass remote building): Document it.
[...]
> +++ b/gnu/services/cuirass.scm
> @@ -72,6 +72,8 @@
> (default "/var/log/cuirass-remote-server.log"))
> (cache cuirass-remote-server-configuration-cache ;string
> (default "/var/cache/cuirass/remote/"))
> + (no-publish? cuirass-remote-server-configuration-no-publish? ;boolean
> + (default #f))
Nitpick: as a rule of thumb, I personally avoid negative options,
otherwise discussions easily end up with phrases like “disable
no-publish” and then you have to think twice before you’re confident
about the meaning. :-)
So I’d suggest turning that into ‘publish?’, defaulting to #t.
Ludo’.
- Re: branch master updated: services: cuirass: Add a no-publish argument.,
Ludovic Courtès <=