From: Maxime Devos <maximedevos@telenet.be>
To: 50979@debbugs.gnu.org
Subject: bug#50979: "home configuration" generated by "guix home import" does not lead to a reproducible home environment
Date: Sat, 02 Oct 2021 22:11:39 +0200 [thread overview]
Message-ID: <bc83fd410f7b46078f58790e5e663c4213568edf.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 1739 bytes --]
Hi,
I ran "guix home import". The output seems mostly reasonable, but the use
of 'local-file' seems troublesome:
;; [comments]
(use-modules [modules])
(home-environment
(packages [stuff])
(services
(list (service
home-bash-service-type
(home-bash-configuration
(bashrc
(list (slurp-file-gexp
(local-file "/home/[USER]/.bashrc"))))
(bash-profile
(list (slurp-file-gexp
(local-file "/home/[USER]/.bash_profile")))))))))
IIUC, when I will run "guix home reconfigure", guix home will intern
~/.bashrc and ~/.bash_profile in the store, build things, and eventually
replace ~/.bashrc with some symlink to something in the store.
I assume this technically all works out, but this seems a bit irreproducible.
What I made modifications to ~/.bash_profile? It seems like, if I run "guix home reconfigure"
on the same system, the modifications will be preserved, which is fine. However,
what if I log into another system, copy the home configuration, and run "guix home reconfigure"
from there? Then "guix home reconfigure" would pick up the ~/.bash_profile from the new system
(without the modifications) instead of the old system, right?
Then the home configuration generated by "guix home import" isn't self-contained,
which seems unfortunate.
Two proposals for addressing the issue:
(1) Use 'plain-file' instead of 'local-file', to include the contents of ~/.bashrc inside
the generated configuration
(2) Let "guix home import" create a directory with the "home-environment.scm", ".bashrc"
and ".bash_profile".
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
reply other threads:[~2021-10-02 20:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bc83fd410f7b46078f58790e5e663c4213568edf.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=50979@debbugs.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 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.