From: Mathieu Othacehe <m.othacehe@gmail.com>
To: 41839@debbugs.gnu.org
Cc: Mathieu Othacehe <othacehe@gnu.org>
Subject: [bug#41839] [PATCH 0/2] ci: Build Guix System images.
Date: Sat, 13 Jun 2020 21:40:01 +0200 [thread overview]
Message-ID: <20200613194001.9580-1-othacehe@gnu.org> (raw)
Hello,
Now that we have a new shiny new "image" record that contains all the required
informations to build or cross-build a Guix System image, it would be nice if
Cuirass could provide associated substitutes.
This serie allows to build a list of Guix System images in the CI. For now
this list only contains the Hurd barebones Guix System image.
Thanks,
Mathieu
Mathieu Othacehe (2):
image: Move hurd image definition to a dedicated file.
ci: Build Guix System images.
gnu/ci.scm | 69 +++++++++++++++++-----------------
gnu/image.scm | 2 +
gnu/local.mk | 2 +
gnu/system/image.scm | 23 +++---------
gnu/system/images/hurd.scm | 76 ++++++++++++++++++++++++++++++++++++++
5 files changed, 121 insertions(+), 51 deletions(-)
create mode 100644 gnu/system/images/hurd.scm
--
2.26.2
next reply other threads:[~2020-06-13 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 19:40 Mathieu Othacehe [this message]
2020-06-13 19:41 ` [bug#41839] [PATCH 1/2] image: Move hurd image definition to a dedicated file Mathieu Othacehe
2020-06-13 19:41 ` [bug#41839] [PATCH 2/2] ci: Build Guix System images Mathieu Othacehe
2020-06-23 21:48 ` Ludovic Courtès
2020-06-25 10:02 ` bug#41839: " Mathieu Othacehe
2020-06-23 21:47 ` [bug#41839] [PATCH 1/2] image: Move hurd image definition to a dedicated file Ludovic Courtès
2020-06-25 9:54 ` Mathieu Othacehe
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=20200613194001.9580-1-othacehe@gnu.org \
--to=m.othacehe@gmail.com \
--cc=41839@debbugs.gnu.org \
--cc=othacehe@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 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).