unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 41839@debbugs.gnu.org
Subject: [bug#41839] [PATCH 1/2] image: Move hurd image definition to a dedicated file.
Date: Tue, 23 Jun 2020 23:47:18 +0200	[thread overview]
Message-ID: <87sgelxxnd.fsf@gnu.org> (raw)
In-Reply-To: <20200613194140.10367-1-othacehe@gnu.org> (Mathieu Othacehe's message of "Sat, 13 Jun 2020 21:41:39 +0200")

Hi!

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> This moves hurd-disk-image to a dedicated file. It also defines a default
> operating-system so that the image can be built standalone.
>
> * gnu/system/images/hurd.scm: New file,
> * gnu/local.mk (GNU_SYSTEM_MODULES): add it.
> * gnu/image.scm (<image>)[name]: New field.
> * gnu/system/image.scm (root-offset, root-label): Export it,
> (hurd-disk-image): remove it as this is now defined in the new, Hurd dedicated
> file above,
> (find-image): adapt to avoid loop dependency.

LGTM!

It would be good to check by running “make as-derivation” if gnu/image/*
gets included.

Ludo’.




  parent reply	other threads:[~2020-06-23 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 19:40 [bug#41839] [PATCH 0/2] ci: Build Guix System images Mathieu Othacehe
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   ` Ludovic Courtès [this message]
2020-06-25  9:54     ` [bug#41839] [PATCH 1/2] image: Move hurd image definition to a dedicated file 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=87sgelxxnd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41839@debbugs.gnu.org \
    --cc=m.othacehe@gmail.com \
    --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).