From: "Clément Lassieur" <clement@lassieur.org>
To: Ricardo Wurmus <rekado@elephly.net>, Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org, 30728@debbugs.gnu.org,
Tatiana Sholokhova <tanja201396@gmail.com>
Subject: Re: bug#30728: Modification for guix installation script.
Date: Mon, 26 Mar 2018 14:59:30 +0200 [thread overview]
Message-ID: <87bmfb9eml.fsf@lassieur.org> (raw)
In-Reply-To: <87fu4ngq0a.fsf@elephly.net>
Hi Ricardo and Marius,
Marius Bakke <mbakke@fastmail.com> writes:
> The binary installation tarball only comes with a profile for 'root'.
Indeed, but it's easy to copy it for any user isn't it?
> The problem is that the installation script assumes $HOME will expand to
> ~root when sourcing the profile, but as you found that isn't always the
> case.
>
> ~root/.guix-profile is "hard-coded" many other places in the script, so
> Tatianas solution seems sensible to me.
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Clément,
>
>> As I said to Chris (Cc'ed), I don't think it's a good idea to install
>> Guix in root's home directory. Instead, we should probably honor the
>> USER and HOME environment variables, so that the command can be run as a
>> non-root user (with sudo) in a consistent way. What do you think?
>
> The script should be run as root as it follows the manual’s
> instructions, which tell people to install Guix for the root user and
> then make it available system-wide.
>
> This is why I think that it would be correct to install it to the root’s
> home directory and not to the sudoing user’s HOME.
>
> Or am I missing something?
Thank you both for your comments. :-)
What I dislike with the present state of things is the need for Guix to
be installed within root's directory. For two reasons :
1. I don't think a command should ever install something in another
user's home directory. The home directory of a user is for things
that are specific to that user, I believe.
2. Users need to update the root profile if they want to update the
Guix daemon, which is cumbersome.
The systemd configuration file must know where to find the Guix daemon.
If it's not in ~root, it must be in the user's home directory. Either
way, the Guix daemon, which is system-wide, still depends on a user.
(A way to make the daemon user-independant would be to add a new command
that would update, say, /var/guix/guix-daemon, with the systemd
configuration file pointing to it.)
I personally prefer that the Guix daemon points to my home directory
because I don't want to update root's profile. Some other people might
prefer that it points to ~root because they might later delete their
profile and want Guix to keep working.
Do we have to take a decision here? Can't we just let the user decide
by letting them customize their environment variables? I think it is
the point of environment variables: giving freedom to users.
next prev parent reply other threads:[~2018-03-26 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 9:04 Modification for guix installation script Tatiana Sholokhova
2018-03-24 16:46 ` Vincent Legoll
2018-03-24 17:00 ` Tatiana Sholokhova
2018-03-24 17:05 ` Vincent Legoll
2018-03-24 21:26 ` Tatiana Sholokhova
2018-03-25 15:26 ` bug#30728: " Ricardo Wurmus
2018-03-25 18:57 ` Mark H Weaver
2018-03-25 18:57 ` bug#30728: " Mark H Weaver
2018-03-26 8:27 ` Clément Lassieur
2018-03-26 8:27 ` Clément Lassieur
2018-03-26 9:11 ` bug#30728: " Ricardo Wurmus
2018-03-26 12:59 ` Clément Lassieur [this message]
2018-03-26 16:09 ` Tatiana Sholokhova
2018-03-26 16:09 ` Tatiana Sholokhova
2018-03-29 8:24 ` Clément Lassieur
2018-03-26 12:59 ` Clément Lassieur
2018-03-27 11:53 ` Gábor Boskovits
2018-03-27 11:53 ` Gábor Boskovits
2018-03-29 8:11 ` Clément Lassieur
2018-03-29 8:11 ` bug#30728: " Clément Lassieur
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=87bmfb9eml.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=30728@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=rekado@elephly.net \
--cc=tanja201396@gmail.com \
/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.