From: "Ludovic Courtès" <ludo@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 53210@debbugs.gnu.org
Subject: bug#53210: installer: referring to N-1 guix is problematic.
Date: Tue, 09 Aug 2022 15:26:12 +0200 [thread overview]
Message-ID: <87v8r17dl7.fsf_-_@gnu.org> (raw)
In-Reply-To: <20220214092908.16801-1-dev@jpoiret.xyz> (Josselin Poiret's message of "Mon, 14 Feb 2022 10:29:04 +0100")
Hi Josselin & all,
I ended up pushing the following patches:
fdafd40432 maint: Use a pretty version string in ISO and VM images.
95a03aa5c5 system: install: Always use 'current-guix'.
57f1892d36 gnu: guix: Default 'current-guix' is built using the current channels.
64a070717c channels: Add 'repository->guix-channel'.
cf60a0a906 build-system/channel: Accept a channel or instance as the source.
5bce4c8242 build-system: Add 'channel-build-system'.
The basics are similar to what you had posted. It adds a useful default
for ‘current-guix’: a package built from the ‘guix’ channel as returned
by ‘guix describe’. In turn, ‘%installation-os’ in (gnu system install)
is changed to use (current-guix) instead of the ‘guix’ package, meaning
that:
guix system image gnu/system/install.scm
and:
./pre-inst-env guix system image gnu/system/install.scm
both produce an image that contains the current Guix.
That allows us to remove the second ‘update-guix-package.scm’ + ‘git
commit’ invocation in ‘make release’, which should make the whole
process faster.
Note that the default for installed systems remains the ‘guix’ package,
not (current-guix). The main reason is that the “Computing derivation”
step when using (current-guix) is too high to do that by default. We
could mitigate that by caching the result of that step more
systematically, but I think that can come later.
Let me know if you have comments!
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-08-09 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:23 bug#53210: installer: referring to N-1 guix is problematic Mathieu Othacehe
2022-01-12 17:41 ` Ludovic Courtès
2022-02-14 9:29 ` bug#53210: [WIP PATCH 0/4] Make current-guix work when run outside a Git checkout Josselin Poiret via Bug reports for GNU Guix
2022-02-14 9:29 ` bug#53210: [WIP PATCH 1/4] gnu: ci: Move generic channel building code Josselin Poiret via Bug reports for GNU Guix
2022-02-14 17:12 ` Ludovic Courtès
2022-02-14 9:29 ` bug#53210: [WIP PATCH 2/4] gnu: Rename channel-build-system and channel-source->package Josselin Poiret via Bug reports for GNU Guix
2022-07-18 19:35 ` bug#53210: installer: referring to N-1 guix is problematic Ludovic Courtès
2022-02-14 9:29 ` bug#53210: [WIP PATCH 3/4] gnu: current-guix: Support when running outside a checkout Josselin Poiret via Bug reports for GNU Guix
2022-02-14 17:15 ` Ludovic Courtès
2022-02-14 9:29 ` bug#53210: [WIP PATCH 4/4] gnu: package-management: Memoize current-guix Josselin Poiret via Bug reports for GNU Guix
2022-02-14 17:10 ` bug#53210: [WIP PATCH 0/4] Make current-guix work when run outside a Git checkout Ludovic Courtès
2022-08-09 13:26 ` Ludovic Courtès [this message]
2022-08-09 19:17 ` bug#53210: installer: referring to N-1 guix is problematic Josselin Poiret via Bug reports for GNU Guix
2022-08-10 10:13 ` Mathieu Othacehe
2022-08-11 14:03 ` Ludovic Courtès
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=87v8r17dl7.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=53210@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--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).