From: "Clément Lassieur" <clement@lassieur.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 30728@debbugs.gnu.org
Subject: bug#30728: guix-install.sh doesn't work if run with "sudo"
Date: Thu, 29 Mar 2018 10:04:32 +0200 [thread overview]
Message-ID: <87d0znwbn3.fsf@lassieur.org> (raw)
In-Reply-To: <87k1txwlfb.fsf@gmail.com>
Chris Marusich <cmmarusich@gmail.com> writes:
> Clément Lassieur <clement@lassieur.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Clément Lassieur <clement@lassieur.org> writes:
>>>
>>>>> The manual says (see: (guix) Binary Installation):
>>>>>
>>>>> 3. Make ‘root’’s profile available under ‘~/.guix-profile’:
>>>>>
>>>>> # ln -sf /var/guix/profiles/per-user/root/guix-profile \
>>>>> ~root/.guix-profile
>>>>
>>>> I think the manual is wrong here. This only makes sense if the user is
>>>> 'root'. Otherwise, the user would expect Guix to be installed in their
>>>> home, not in root's home.
>>>
>>> Step 2 says “As root, run: […]”. “~root” resolves to “/root”, not to
>>> “$HOME/root”, so it even works when run as a regular user.
>>>
>>> The manual seems correct to me and this is what the script aims to
>>> implement.
>>
>> But ~/.guix-profile may resolve to /home/user/.guix-profile. So it
>> should be ~root/.guix-profile instead of ~/.guix-profile.
>
> Ah, I think I now see the cause of our miscommunication.
>
> It's possible to interpret the manual's use of ~ and $HOME to mean "the
> unprivileged user's home directory", instead of "root's home directory".
> I think that's a mistake in the manual, since the "ln" clearly makes
> root's profile available under root's home directory, and the step
> involving $HOME doesn't make sense unless $HOME expands to root's home
> directory.
>
> I've updated my patch; it now also changes the following line...
>
> 3. Make ‘root’’s profile available under ‘~/.guix-profile’:
>
> ...to this:
>
> 3. Make ‘root’’s profile available under ‘~root/.guix-profile’:
>
> How does that sound?
This fixes the documentation inconsistency, but I still think Guix
shouldn't be installed in ~root (as I explain there:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30728#32).
prev parent reply other threads:[~2018-03-29 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zi3lh6mb.fsf@lassieur.org>
2018-03-23 13:20 ` bug#30728: guix-install.sh doesn't work if run with "sudo" Clément Lassieur
2018-03-25 5:16 ` Chris Marusich
2018-03-26 8:05 ` Clément Lassieur
2018-03-26 9:18 ` Marius Bakke
2018-03-27 7:46 ` Ricardo Wurmus
2018-03-27 9:11 ` Clément Lassieur
2018-03-27 16:08 ` Chris Marusich
2018-03-28 19:24 ` Ricardo Wurmus
2018-03-29 5:07 ` Chris Marusich
2018-03-29 8:26 ` Clément Lassieur
2018-03-29 7:48 ` Clément Lassieur
2018-03-29 10:07 ` Ricardo Wurmus
2018-03-30 22:07 ` Clément Lassieur
2018-03-29 8:04 ` Clément Lassieur [this message]
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=87d0znwbn3.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=30728@debbugs.gnu.org \
--cc=cmmarusich@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.