unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 47401@debbugs.gnu.org
Subject: [bug#47401] [PATCH] doc: Mention value /etc to sysconfdir option.
Date: Wed, 31 Mar 2021 08:10:40 +0100	[thread overview]
Message-ID: <87r1jvztlb.fsf@cbaines.net> (raw)
In-Reply-To: <20210326060138.27179-1-zimon.toutoune@gmail.com>

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


zimoun <zimon.toutoune@gmail.com> writes:

> * doc/contributing.texi (Building from Git): Mention value /etc to sysconfdir
> option.
> ---
>
> Hi,
>
> From a discussion [1] about a reproducibility issue,
>
>         As discussed on IRC, ‘guix pull’ preserves the settings of the host
>         Guix.  So if your initial ‘guix’ has %sysconfdir set to
>         /usr/local/etc, ‘guix pull’ will preserve that.
>
>         It turns out that, as is always the case with GNU Standards compliant
>         configure script, the default value for --prefix is /usr/local, and
>         the default for --sysconfdir is $prefix/etc.
>
>         Mostly likely, what happened is that at some point you built Guix from
>         source using the default prefix and sysconfdir, and then you ran ‘guix
>         pull’ from that Guix.
>
> I discovered that the option ’sysconfdir’ at ./configure time is set by
> default to /usr/local/etc conforming the GNU Coding standards.  And Guix
> expect instead /etc.  As 'localstadir', it is unconventional.
>
> The manual does not mention this subtility.  This patch adds a tiny sentence
> to avoid the trap for the attentive reader.
>
> 1: <https://yhetil.org/guix/877dnqe3to.fsf@gnu.org>
>
>
> Thanks,
> simon
>
>  doc/contributing.texi | 8 ++++++--
>  doc/guix.texi         | 2 +-
>  2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/doc/contributing.texi b/doc/contributing.texi
> index 58c4dafb9b..53840d81cc 100644
> --- a/doc/contributing.texi
> +++ b/doc/contributing.texi
> @@ -228,8 +228,12 @@ necessary to support this, including @env{PATH} and @env{GUILE_LOAD_PATH}.
>  Note that @command{./pre-inst-env guix pull} does @emph{not} upgrade the
>  local source tree; it simply updates the @file{~/.config/guix/current}
>  symlink (@pxref{Invoking guix pull}).  Run @command{git pull} instead if
> -you want to upgrade your local source tree.
> -
> +you want to upgrade your local source tree.  Moreover, note also that
> +@command{guix pull} preserves the settings of the host Guix.  For
> +instance, regular Guix passes @code{--sysconfdir=/etc/}, whereas the GNU
> +Coding Standards sets by default @var{prefix} to @file{/usr/local} and
> +@var{sysconfdir} to @file{$prefix/etc} (@pxref{Directory Variables,,,
> +standards, GNU Coding Standards}).

I think this is maybe useful to note somewhere, but not to add to the
existing paragraph here.

The paragraph starting on line 228 looks to me to be aimed at new users
who might be at risk of confusing guix pull and git pull, whereas the
bit you're adding is about something completely different, explaining a
subtlety of running guix pull (something an earlier part of the
paragraph is saying not to run).

Maybe there is a more appropriate place in the main manual?

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

      reply	other threads:[~2021-03-31  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  6:01 [bug#47401] [PATCH] doc: Mention value /etc to sysconfdir option zimoun
2021-03-31  7:10 ` Christopher Baines [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=87r1jvztlb.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=47401@debbugs.gnu.org \
    --cc=zimon.toutoune@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).