From: "Clément Lassieur" <clement@lassieur.org>
To: Tatiana Sholokhova <tanja201396@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, 30728@debbugs.gnu.org
Subject: bug#30728: Modification for guix installation script.
Date: Thu, 29 Mar 2018 10:24:57 +0200 [thread overview]
Message-ID: <87a7urwap2.fsf@lassieur.org> (raw)
In-Reply-To: <CAMSS15DgqNa3j7OA1=brmomBnqG40xi6CK1G_pXgAZACozteaA@mail.gmail.com>
Hi Tatiana,
Tatiana Sholokhova <tanja201396@gmail.com> writes:
> Hello!
>
>
> Could you please make that change on top of the current version of the
> Guix sources as a git commit? Then you can run “git format-patch -1” to
> format it as a patch in a format that we can apply. You can send the
> resulting patch file as an attachment to a reply to this email.
> This also fixes bug #30728, so please add this line to the commit
> message:
> --
> Ricardo
>
>
> I have attached the patch file to this email. This patch fixes the installation
> process but it placeguixwithin root's directory.
>
>
> 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.
>
>
> We can further work on the script's flexibility using the environment variable
> solution.
Thank you for your patch. The one Chris did has been pushed, but if you
want, you can still work on improving the script's flexibility. I still
haven't seen any valid argument for or against it, though, so I don't
know if it's a good idea. Maybe we can wait until someone says
something about it!
Clément
next prev parent reply other threads:[~2018-03-29 8:25 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 [this message]
2018-03-27 11:53 ` Gábor Boskovits
[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=87a7urwap2.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=30728@debbugs.gnu.org \
--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 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).