From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: two ill effects of maint.mk
Date: Thu, 10 Jun 2021 09:09:30 -0700 [thread overview]
Message-ID: <107ba812-c46d-243b-4644-bc3f17f0a89d@cs.ucla.edu> (raw)
In-Reply-To: <2220832.NeGGHjDtpa@omega>
On 6/10/21 8:41 AM, Bruno Haible wrote:
> The bad effects affect
> * the developers who work from a git checkout + all users of the tarball
> for packages that include GNUmakefile and maint.mk in their tarballs,
> e.g. GNU findutils, GNU guile, GNU gzip, GNU libidn, GNU m4, GNU patch,
> GNU poke.
> * the developers who work from a git checkout only, for the other packages
> that use this module, e.g. GNU emacs, GNU gettext.
As I vaguely recall, that "export LC_ALL = C" was added so that builds
were reproducible, which is a plus. Perhaps we could try to get the best
of both worlds, by changing it to set LC_ALL to an English UTF-8 locale
if available, and the C locale if not. Failing that, I suppose it'd be
OK to simply remove the line and put up with less-reproducible builds.
next prev parent reply other threads:[~2021-06-10 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 15:41 two ill effects of maint.mk Bruno Haible
2021-06-10 16:09 ` Paul Eggert [this message]
2021-06-10 17:12 ` Bruno Haible
2021-06-10 17:14 ` Bruno Haible
2021-06-10 17:21 ` Paul Eggert
2021-06-10 17:34 ` Bruno Haible
2021-06-10 17:38 ` Paul Eggert
2021-06-20 22:15 ` Bruno Haible
2021-06-21 2:47 ` Paul Eggert
2021-06-21 8:52 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=107ba812-c46d-243b-4644-bc3f17f0a89d@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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.
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).