From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Revise EAPI 6? (was: [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability)
Date: Thu, 12 Nov 2015 06:52:24 +0000 (UTC) [thread overview]
Message-ID: <n21cv7$ofs$1@ger.gmane.org> (raw)
In-Reply-To: CAHmME9q0cUeSxThXLaF4du64_AN7Xcc5RK6d7HaZxJgqC+CXAA@mail.gmail.com
Jason A. Donenfeld <zx2c4@gentoo.org> wrote:
>
> I'd be in favor of full-on LC_ALL=C.
Setting LC_ALL seems wrong as it is meant as a quick hack
and should not be relied on by a "generic" tool like portage.
Better define to *unset* LC_ALL (remembering the previous value,
see below) and to set (all?) other LC_* to defined values.
When we are at it: Maybe it is even sufficient to define only
LC_CTYPE=C
LC_NUMERIC=C
LC_COLLATE=C
LC_MESSAGES=C
LC_MONETARY=C
In any case, the old values should be kept (and for simplicity
defined to the previous LC_ALL if the latter was set),
so that the ebuild author is able to stick to the user's
choice for certain/all values if he needs to:
In particular, for LC_CTYPE, this might be necessary,
because of correct UTF8-support, as already mentioned
(the ebuild author cannot say LC_CTYPE=*.UTF8).
But also e.g. for LC_MONETARY, this might be necessary for some
strange local banking tools.
It is perhaps not necessary to (re)define LANG at all:
Setting LC_MESSAGES should be sufficient for most build-time
stuff to get readable logs, and LANG=C might be the main reason,
why some people might not like the change and decided e.g.
to patch it out in paludis, as mentioned in this thread.
prev parent reply other threads:[~2015-11-12 6:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 23:53 [gentoo-dev] reminder: you cannot use bash-4.x features (e.g. ${var^^}) in EAPI=[0-5] Mike Frysinger
2015-11-11 1:54 ` Mike Frysinger
2015-11-11 2:51 ` [gentoo-dev] [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability Mike Frysinger
2015-11-11 4:03 ` Mike Frysinger
2015-11-11 4:16 ` Ulrich Mueller
2015-11-11 7:16 ` René Neumann
2015-11-11 7:37 ` Ulrich Mueller
2015-11-11 7:47 ` Mike Frysinger
2015-11-11 8:04 ` Ulrich Mueller
2015-11-11 7:42 ` Mike Frysinger
2015-11-11 6:16 ` Patrick Lauer
2015-11-11 9:13 ` Michał Górny
2015-11-11 12:39 ` Ciaran McCreesh
2015-11-11 15:48 ` [gentoo-dev] Revise EAPI 6? (was: [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability) Ulrich Mueller
2015-11-11 21:52 ` Jason A. Donenfeld
2015-11-11 22:21 ` [gentoo-dev] Revise EAPI 6? Matthias Maier
2015-11-11 23:18 ` Ulrich Mueller
2015-11-12 0:34 ` Mike Gilbert
2015-11-12 6:24 ` Ulrich Mueller
2015-11-12 6:52 ` Martin Vaeth [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='n21cv7$ofs$1@ger.gmane.org' \
--to=martin@mvath.de \
--cc=gentoo-dev@lists.gentoo.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