unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 39501-done@debbugs.gnu.org
Subject: bug#39501: [PATCH] doc: Clarify how sudo and guix interact when updating
Date: Fri, 14 Feb 2020 19:15:23 +0100	[thread overview]
Message-ID: <20200214181523.55x3dphr4jg6oo5x@gravity> (raw)
In-Reply-To: <87pneh6sge.fsf@devup.no>

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

On Fri, Feb 14, 2020 at 05:31:45PM +0100, Marius Bakke wrote:
> Jakub Kądziołka <kuba@kadziolka.net> writes:
> 
> > * doc/guix.texi (After System Installation): Explicitly explain the
> >   mechanics of how sudo differs from a login shell.
> >
> > Some recent discussions on IRC suggest that the existing wording wasn't
> > entirely clear.
> > ---
> >  doc/guix.texi | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/doc/guix.texi b/doc/guix.texi
> > index 710cf97673..9f758706f6 100644
> > --- a/doc/guix.texi
> > +++ b/doc/guix.texi
> > @@ -72,6 +72,7 @@ Copyright @copyright{} 2019 Guillaume Le Vaillant@*
> >  Copyright @copyright{} 2020 Leo Prikler@*
> >  Copyright @copyright{} 2019, 2020 Simon Tournier@*
> >  Copyright @copyright{} 2020 Wiktor Żelazny@*
> > +Copyright @copyright{} 2020 Jakub Kądziołka@*
> >  
> >  Permission is granted to copy, distribute and/or modify this document
> >  under the terms of the GNU Free Documentation License, Version 1.3 or
> > @@ -2439,6 +2440,11 @@ your system includes the latest security updates (@pxref{Security Updates}).
> >  Note that @command{sudo guix} runs your user's @command{guix} command and
> >  @emph{not} root's, because @command{sudo} leaves @code{PATH} unchanged.  To
> >  explicitly run root's @command{guix}, type @command{sudo -i guix @dots{}}.
> > +
> > +The difference matters here, because @command{guix pull} updates
> > +the @command{guix} command and package definitions only for the user it is ran
> > +as. This means that if you choose to use @command{guix system reconfigure} in
>      ^^^
> Please use two spaces after punctuations.  Otherwise LGTM.

Thanks! I added a space and pushed to master as
6a7f4d89b2029b43b766217d71d5dbbdfcc5fa09.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-02-14 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 21:47 [bug#39501] [PATCH] doc: Clarify how sudo and guix interact when updating Jakub Kądziołka
2020-02-14 16:31 ` Marius Bakke
2020-02-14 18:15   ` Jakub Kądziołka [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

  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=20200214181523.55x3dphr4jg6oo5x@gravity \
    --to=kuba@kadziolka.net \
    --cc=39501-done@debbugs.gnu.org \
    --cc=mbakke@fastmail.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).