From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>, 43049@debbugs.gnu.org
Subject: bug#43049: Add the ability to install Guix System offline
Date: Sat, 10 Feb 2024 11:13:06 +0100 [thread overview]
Message-ID: <87eddk630t.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87wmrga9mw.fsf@xelera.eu>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Hi Giovanni,
Giovanni Biscuolo <g@xelera.eu> writes:
>> However, we also implemented the `current-guix` hack that basically uses
>> a guix checkout at the current guix version as the source for the guix
>> package.
>
> So, since some commit, now the guix version used to build the target
> system image is the one checked-out by the person/agent running the
> install image build script: did I understand it correctly?
Yes.
>> In both cases though, we shouldn't see any differences in other
>> package's derivations…
>
> Does this mean you consider possible to pre-populate the /gnu/store
> install system (the one started using the install image) with a substet
> of substitutes possibly needed in the target system?
I think it's already meant to be the case, see the comment in
gnu/system/install.scm about keeping a reference to the bare bones os's
closure. It wouldn't contain all graphical stuff either, but I think
there's also some trouble with grafts that forces users to still
download substitutes.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
prev parent reply other threads:[~2024-02-10 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 20:03 guix installation why internet connection required? vvt
2023-12-29 4:06 ` Maxim Cournoyer
2024-02-05 17:33 ` Giovanni Biscuolo
2024-02-06 10:58 ` bug#43049: " Josselin Poiret via Bug reports for GNU Guix
2024-02-07 9:47 ` bug#43049: Add the ability to install Guix System offline Giovanni Biscuolo
2024-02-10 10:13 ` Josselin Poiret via Bug reports for GNU Guix [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eddk630t.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=43049@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=g@xelera.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.