all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
	30728@debbugs.gnu.org, Tatiana Sholokhova <tanja201396@gmail.com>
Subject: bug#30728: Modification for guix installation script.
Date: Thu, 29 Mar 2018 10:11:35 +0200	[thread overview]
Message-ID: <87bmf7wbbc.fsf__5100.67382497272$1522311060$gmane$org@lassieur.org> (raw)
In-Reply-To: <CAE4v=piKxgvUEdjnb_2_GzS8fs5NgFSGB65HezeRdLyVan84JQ@mail.gmail.com>

Gábor Boskovits <boskovits@gmail.com> writes:

> 2018-03-26 11:11 GMT+02:00 Ricardo Wurmus <rekado@elephly.net>:
>
>>
>> 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?
>>
>>
> I think Ricardo is right on this one. I would also recommend installing in
> root's home directory.

But you don't explain why.  And "as it follows the manual's
instructions" isn't a good reason to me.

> I believe, that installing in a user home would make sense only with a
> big amount of additional instrumentation and documentation changes,
> along with arrangements to allow guix in userspace.

I think it would be fairly easy.  The kind of edit we do all the time
when patches are being reviewed.

  reply	other threads:[~2018-03-29  8:12 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   ` Mark H Weaver
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
2018-03-26 16:09       ` Tatiana Sholokhova
2018-03-29  8:24         ` Clément Lassieur
2018-03-26 16:09       ` Tatiana Sholokhova
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 [this message]
2018-03-29  8:11       ` Clément Lassieur
2018-03-26  8:27 ` 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='87bmf7wbbc.fsf__5100.67382497272$1522311060$gmane$org@lassieur.org' \
    --to=clement@lassieur.org \
    --cc=30728@debbugs.gnu.org \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --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.