[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#74531] [PATCH] system: Add "installer" sub-command.
From: |
Janneke Nieuwenhuizen |
Subject: |
[bug#74531] [PATCH] system: Add "installer" sub-command. |
Date: |
Tue, 03 Dec 2024 09:15:52 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Mathieu Othacehe writes:
> Hello Janneke,
>
>> Subject: [PATCH] system: Add "installer" sub-command.
>>
>> * guix/scripts/system/installer.scm: New file.
>> * Makefile.am (MODULES)[ENABLE_INSTALLER]: Register it.
>> (MODULES_NOT_COMPILED)[!ENABLE_INSTALLER]: Likewise.
>> * guix/scripts/system.scm (show-help): Add help for "installer" sub-command.
>> (actions): Register "installer".
>> (guix-system): Invoke `guix-system-installer' sub-command.
>> * doc/guix.texi (Invoking guix system): Document it.
>> * gnu/installer.scm (run-installer): Remove "./pre-inst env".
>
> That looks great thanks!
Your idea :)
> It makes me think that we could go further than that an come-up with a
> command that would look like:
>
> guix system image --installer os-1.scm os-2.scm
>
> That would generate a bootable image, that would contain the closure of
> all the provided system configurations (os-1.scm, os-2.scm, ...).
Oh, that would be nice too, would you like to look into that?
> That image would run the installer and would directly propose the
> installation of the os-1 or the os-2 to the user. Most of the
> installations pages could then be skipped, except the host-name and
> partitioning pages.
>
> That way, one could generate an image with say, a Hurd based system
> configuration and a Linux based system configuration and then, pick in
> the installer the system to be installed. As the image contains the
> closure of both systems, there would be no network issues.
Yes, indeed!
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | AvatarĀ® https://AvatarAcademy.com