From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Providing a Guix System images catalog.
Date: Tue, 26 May 2020 09:13:51 +0200 [thread overview]
Message-ID: <871rn7w4ls.fsf@gnu.org> (raw)
In-Reply-To: <87pnarr7ka.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 26 May 2020 00:08:53 +0200")
Hey,
>> That's pretty nice!
>
> +1!
Thanks to both of you for your quick feedback!
>> I wonder about how this composes; if I'd want to add say a guix-daemon
>> service to the bare-hurd, how would I do that?
>
> How about leaving the ‘operating-system’ field of <image> to #f or some
> default value, and then filling it in with the argument passed to ‘guix
> system’?
>
> Or better: at the API level, we’d look for an “image constructor” (or
> “image type”), not an image, where an image constructor is a procedure
> that takes an <operating-system> and returns an <image>. In practice,
> you’d wrap that in <image-type> with a ‘name’ field so you can still
> look them up by name.
This sounds fair. However, I would still like that:
* The operating-systems are stored elsewhere than in an "examples"
directory.
* The "image" command could use a default operating-system that we are
building with the CI, and making available on Guix website.
What about having a:
--8<---------------cut here---------------start------------->8---
gnu/system/images/hurd
├── hurd-bare-bones-os.scm
└── hurd.scm
--8<---------------cut here---------------end--------------->8---
hurd-bare-bones-os.scm would contain an operating-system with the
"image-type" set to the image contained in hurd.scm.
Conversely, the image in hurd.scm would point to the default
operating-system, that could be the one in hurd-bare-bones-os.scm.
Then, the user could type:
--8<---------------cut here---------------start------------->8---
guix system image hurd-disk-image
guix system disk-image hurd-bare-bones-os.scm
--8<---------------cut here---------------end--------------->8---
and have the same result.
We could also allow:
--8<---------------cut here---------------start------------->8---
guix system image hurd-disk-image --with-os hurd-bare-bones-os.scm
--8<---------------cut here---------------end--------------->8---
to override the default operating-system.
WDYT?
Thanks,
Mathieu
next prev parent reply other threads:[~2020-05-26 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 15:30 Providing a Guix System images catalog Mathieu Othacehe
2020-05-25 20:42 ` Jan Nieuwenhuizen
2020-05-25 22:08 ` Ludovic Courtès
2020-05-26 7:13 ` Mathieu Othacehe [this message]
2020-06-23 8:17 ` 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=871rn7w4ls.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).