all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 28487@debbugs.gnu.org
Subject: [bug#28487] [PATCH] cuirass: Add gnu-system build spec.
Date: Tue, 26 Sep 2017 10:18:44 +0200	[thread overview]
Message-ID: <87zi9h27q3.fsf@gnu.org> (raw)
In-Reply-To: <20170917201157.9802-5-janneke@gnu.org> (Jan Nieuwenhuizen's message of "Sun, 17 Sep 2017 22:11:57 +0200")

Hello!

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> * build-aux/cuirass/gnu-system.scm: New file.  Combines
> build-aux/hydra/gnu-system.scm, guix-cuirass/examples/gnu-system.scm and supports
> building a named subset.
>
>      (let ((spec #~((#:name . "guix")
>                     (#:url . "git://git.savannah.gnu.org/guix.git")
>                     (#:load-path . ".")
>                     (#:file . "build-aux/cuirass/gnu-system.scm")
>                     (#:proc . hydra-jobs)
>                     (#:arguments (subset . ("hello" "grep")))
>                     (#:branch . "master"))))
>        (service cuirass-service-type
>                 (cuirass-configuration
>                  (specifications #~(list '#$spec)))))

I like this but… while we’re at it, could we arrange to have a single
file that works for both Hydra and Cuirass?

Concretely, we currently have these two files:

  https://git.savannah.gnu.org/cgit/guix.git/tree/build-aux/hydra/gnu-system.scm
  https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/cuirass-jobs.scm

There are very close to one another.  The main difference is that one
returns an alist with symbols, whereas the other returns an alist with
keywords.

If we could instead add, say, build-aux/hydra/gnu-system-cuirass.scm,
which simply loads gnu-system.scm and “converts” the resulting alist
appropriately, that would be awesome.

I understand this is not quite what you were asking for ;-), but it
would achieve the same result.

How does that sound?

Thanks,
Ludo’.

  reply	other threads:[~2017-09-26  8:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 20:11 [bug#28484] Some steps and questions for Cuirass Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28485] [PATCH 1/3] base: Make working copy writable Jan Nieuwenhuizen
     [not found]   ` <handler.28485.B.1505679193775.ack@debbugs.gnu.org>
2017-09-18 15:46     ` bug#28485: Acknowledgement ([PATCH 1/3] base: Make working copy writable.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28486] [PATCH 2/3] gnu-system: Accept subset with list of package names Jan Nieuwenhuizen
     [not found]   ` <handler.28486.B.1505679194784.ack@debbugs.gnu.org>
2017-09-18 15:45     ` bug#28486: Acknowledgement ([PATCH 2/3] gnu-system: Accept subset with list of package names.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28488] [PATCH 3/3] base: Show feedback when build has finished Jan Nieuwenhuizen
     [not found]   ` <handler.28488.B.1505679198802.ack@debbugs.gnu.org>
2017-09-18 15:48     ` bug#28488: Acknowledgement ([PATCH 3/3] base: Show feedback when build has finished.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28487] [PATCH] cuirass: Add gnu-system build spec Jan Nieuwenhuizen
2017-09-26  8:18   ` Ludovic Courtès [this message]
2017-09-26 17:56     ` Jan Nieuwenhuizen
2017-09-26 18:05       ` Jan Nieuwenhuizen
2017-09-26 20:29       ` Ludovic Courtès
2017-09-27 18:55         ` Jan Nieuwenhuizen
2017-09-27 19:45           ` Ludovic Courtès
2017-09-27 20:32             ` Jan Nieuwenhuizen
2017-09-27 20:52               ` Jan Nieuwenhuizen
2017-09-28  8:26                 ` Ludovic Courtès
2017-09-28 15:41                   ` bug#28487: " Jan Nieuwenhuizen
2017-09-28  8:27               ` [bug#28487] " Ludovic Courtès
2017-09-28 16:04                 ` Jan Nieuwenhuizen
2017-09-18 11:51 ` [bug#28484] Some steps and questions for Cuirass Mathieu Othacehe
2017-09-18 15:44   ` bug#28484: " Jan Nieuwenhuizen

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=87zi9h27q3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28487@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    /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.