From: EuAndreh <eu@euandre.org>
To: guix-devel@gnu.org
Subject: RFC: Configurable placing of the ~/.guix-home symlink
Date: Fri, 29 Apr 2022 11:44:01 -0300 [thread overview]
Message-ID: <165124344113.9376.12189389163309720556@localhost> (raw)
Hi Guix!
When trying to get a clean $HOME, I see that the ~/.guix-home path is fixed in
the code under gnu/home/*,
usually via (string-append (GETENV "HOME") "/.guix-home").
I want to propose a configurable path to ~/.guix-home, and allow this to be
chosen in the (home-environment ...) declaration. It would expose a
GUIX_HOME_PATH_ENVIRONMENT variable[0] so that one could dynamically retrieve
the path to it, if needed in scripts or similar. The implementation would also
need to be able to handle changes in the (home-environment ...) declaration,
and know when to remove the old symlink from ~/.guix-home to the new path,
similar to what the gnu/home/services/symlink-manager.scm does nowadays.
How do you feel about this? What do you think? Is there a shortcoming,
pitfalls, limitations that this approach entails?
I'm willing do work on the implementation and on tests where applicable, and
send the patches (eventually when I get this done =p). I wanted to raise a
discussion before jumping into the code, even to get input and see how the
community feels about this.
WDYT?
[0]: I'm not picking this name, I just made up to make this more concrete. I'd
look at the existing variable declarations, such as those exposed by
`guix shell` to make it consistent with them.
next reply other threads:[~2022-04-29 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:44 EuAndreh [this message]
2022-05-05 6:44 ` RFC: Configurable placing of the ~/.guix-home symlink Andrew Tropin
2022-05-15 0:07 ` EuAndreh
2022-05-05 6:55 ` Attila Lendvai
2022-05-06 7:26 ` Andrew Tropin
2022-05-15 0:10 ` EuAndreh
2022-05-15 13:15 ` Ludovic Courtès
2022-05-15 15:41 ` EuAndreh
2022-05-23 15:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165124344113.9376.12189389163309720556@localhost \
--to=eu@euandre.org \
--cc=guix-devel@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.