From: Andrew Tropin <andrew@trop.in>
To: Attila Lendvai <attila@lendvai.name>, EuAndreh <eu@euandre.org>
Cc: guix-devel@gnu.org
Subject: Re: RFC: Configurable placing of the ~/.guix-home symlink
Date: Fri, 06 May 2022 10:26:12 +0300 [thread overview]
Message-ID: <87ilqjm8a3.fsf@trop.in> (raw)
In-Reply-To: <kgvZKi4PpUJXDkNumRf3bDXPYx7436BbrqFhAYzHIMALtgoBGcMQ67e53patVaA2Iw4DKKUqLReKZ6NH0JrNoMiGihSt1FFBnABq2TtfUVY=@lendvai.name>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On 2022-05-05 06:55, Attila Lendvai wrote:
>> 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").
>
> FWIW, i was also surprised that the default is not something under ~/.config/guix/
It also can be problematic, we can't hardcode ~/.config/guix home due to
XDG spec, and at the same time XDG_CONFIG_HOME can be managed by Guix
Home, but also can be set outside, and all the points mentioned above
applicable here as well.
Back in the day, the implementation of Guix Home required a symlink in
home directory, right now due to improvements in symlink-manager and
reconfigure code it's probably not necessary and with a few patches
/var/guix/profiles/per-user/bob/guix-home/ can be used instead.
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next prev parent reply other threads:[~2022-05-06 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:44 RFC: Configurable placing of the ~/.guix-home symlink EuAndreh
2022-05-05 6:44 ` Andrew Tropin
2022-05-15 0:07 ` EuAndreh
2022-05-05 6:55 ` Attila Lendvai
2022-05-06 7:26 ` Andrew Tropin [this message]
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
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=87ilqjm8a3.fsf@trop.in \
--to=andrew@trop.in \
--cc=attila@lendvai.name \
--cc=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 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).