unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>,
	30728@debbugs.gnu.org, "Clément Lassieur" <clement@lassieur.org>,
	"Tatiana Sholokhova" <tanja201396@gmail.com>
Subject: bug#30728: Modification for guix installation script.
Date: Tue, 27 Mar 2018 13:53:32 +0200	[thread overview]
Message-ID: <CAE4v=piKxgvUEdjnb_2_GzS8fs5NgFSGB65HezeRdLyVan84JQ__38824.0386652344$1522151539$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <87fu4ngq0a.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

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. Ibelieve, 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. This is a straightforward way to make the script do what it's
purpose is.


> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1991 bytes --]

  parent reply	other threads:[~2018-03-27 11:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMSS15DTAQJXy_OrPuHfpmgd_S-bc5=JfexoNyxe=yH8RKiF4g@mail.gmail.com>
2018-03-25 15:26 ` bug#30728: Modification for guix installation script Ricardo Wurmus
2018-03-25 18:57   ` Mark H Weaver
2018-03-26  8:27 ` Clément Lassieur
     [not found] ` <87d0zr9r76.fsf@lassieur.org>
2018-03-26  9:11   ` Ricardo Wurmus
2018-03-26 12:59     ` Clément Lassieur
     [not found]     ` <87bmfb9eml.fsf@lassieur.org>
2018-03-26 16:09       ` Tatiana Sholokhova
     [not found]       ` <CAMSS15DgqNa3j7OA1=brmomBnqG40xi6CK1G_pXgAZACozteaA@mail.gmail.com>
2018-03-29  8:24         ` Clément Lassieur
2018-03-27 11:53     ` Gábor Boskovits [this message]
     [not found]     ` <CAE4v=piKxgvUEdjnb_2_GzS8fs5NgFSGB65HezeRdLyVan84JQ@mail.gmail.com>
2018-03-29  8:11       ` 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

  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='CAE4v=piKxgvUEdjnb_2_GzS8fs5NgFSGB65HezeRdLyVan84JQ__38824.0386652344$1522151539$gmane$org@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=30728@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=guix-devel@gnu.org \
    --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 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).