From: Christopher Allan Webber <cwebber@dustycloud.org>
To: John Darrington <jmd@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] $HOME/.guix-profile considered harmful.
Date: Mon, 12 Sep 2016 20:32:31 -0500 [thread overview]
Message-ID: <87k2eg4ma8.fsf@dustycloud.org> (raw)
In-Reply-To: <1473704299-8703-1-git-send-email-jmd@gnu.org>
John Darrington writes:
> I have my /home NFS mounted (not uncommon in large networks, I think).
> Unfortunately this does not play nicely with guix's convention of setting
> $PATH &c to $HOME/.guix-profile and then linking $HOME/.guix-profile to
> %state-directory/profiles/per-user/$USER/guix_profile - for the obvious reason
> that %state-directory could be different on each workstation - in which case
> $HOME/.guix-profile will be a dead link.
>
> I'm not sure exactly what benefit the ~/.guix-profile convention brings us, except
> perhaps that it is easy to remember.
>
> I'd like to see the ability to have GuixSD deployable in medium-large intranets
> where home (and /var/mail) are remotely mounted filesystems. Hence I suggest that
> $HOME/.guix-profile is deprecated.
Hm, considered harmful, I dunno. It seems a bit strong! Something does
feel useful to me about having it in $HOME. It seems like the logical
place to me, since it's per-user.
But I can see the merits of moving it to the %state-directory.
Eventually Debian + Guix stopped working with my GuixSD setup. It might
have been nice to have a separate store location altogether.
Still, this switch feels very strange to me. $HOME feels... like the
right thing. Which I guess isn't a very good explaination.
next prev parent reply other threads:[~2016-09-13 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 18:18 [PATCH] $HOME/.guix-profile considered harmful John Darrington
2016-09-13 1:32 ` Christopher Allan Webber [this message]
2016-09-13 8:35 ` Vincent Legoll
2016-09-13 17:47 ` Ricardo Wurmus
2016-09-13 21:23 ` 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=87k2eg4ma8.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
--cc=jmd@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.