From: "Ludovic Courtès" <ludo@gnu.org>
To: Richard Sent <richard@freakingpenguin.com>
Cc: guix-devel@gnu.org
Subject: Re: Changing the defaults for --localstatedir and --sysconfdir?
Date: Thu, 02 May 2024 11:00:15 +0200 [thread overview]
Message-ID: <87sez0zizk.fsf@gnu.org> (raw)
In-Reply-To: <87sez19s1o.fsf@freakingpenguin.com> (Richard Sent's message of "Wed, 01 May 2024 16:49:07 -0400")
Hi Richard,
Richard Sent <richard@freakingpenguin.com> skribis:
> As everyone who's built Guix from source knows, when running ./configure
> on a system with an existing Guix installation you must remember to
> specify --localstatedir=/var and --sysconfdir=/etc. I think we should
> consider whether those variables should default to those values.
I think it would make sense.
Before I advocated that we should preferably stick to the GNU standards
and have users make informed choices (that’s how we ended up with the
‘GUIX_CHECK_LOCALSTATEDIR’ macro that warns users but lets them
explicitly pass ‘--localstatedir’.)
That was 8 years ago though (eight!). At this point I think defaulting
to /var and /etc would do more good than harm.
What do others think?
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-05-02 9:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 20:49 Changing the defaults for --localstatedir and --sysconfdir? Richard Sent
2024-05-02 9:00 ` Ludovic Courtès [this message]
2024-05-02 9:11 ` Attila Lendvai
2024-05-02 23:23 ` Romain
2024-05-02 11:31 ` Janneke Nieuwenhuizen
2024-05-02 18:14 ` Vagrant Cascadian via Development of GNU Guix and the GNU System distribution.
2024-05-02 12:58 ` Andreas Enge
2024-05-02 16:37 ` Efraim Flashner
2024-05-06 10:06 ` Ludovic Courtès
2024-05-02 16:35 ` Efraim Flashner
2024-06-07 12:54 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-09 0:58 ` Maxim Cournoyer
2024-05-03 10:10 ` Ricardo Wurmus
2024-05-06 10:08 ` Ludovic Courtès
2024-05-07 20:07 ` Simon Tournier
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=87sez0zizk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=richard@freakingpenguin.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).