Archives
Archives
| From: | Ulrich Mueller <ulm@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability | ||
| Date: | Wed, 11 Nov 2015 04:16:23 | ||
| Message-Id: | 22082.49419.148679.628538@a1i15.kph.uni-mainz.de | ||
| In Reply to: | [gentoo-dev] [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability by Mike Frysinger |
||
| 1 | >>>>> On Tue, 10 Nov 2015, Mike Frysinger wrote: |
| 2 | |
| 3 | > Arfrever highlights these are not even safe to use. bash is locale aware, |
| 4 | > so it'll apply LC_COLLATE rules when processing the ^/, casemods. while |
| 5 | > you can fix this with external programs ala: |
| 6 | > LC_COLLATE=C tr ... |
| 7 | |
| 8 | > you can't do it with inline code like: |
| 9 | > LC_COLLATE=C SRC_URI=".../${PN^^}/..." |
| 10 | |
| 11 | >>>>> On Tue, 10 Nov 2015, Mike Frysinger wrote: |
| 12 | |
| 13 | > sorry, i meant char classification here (LC_CTYPE), not collation. |
| 14 | |
| 15 | Shouldn't these be safe to use if the string consists purely of ASCII |
| 16 | characters? I mean, A-Z and a-z should be uppercase and lowercase, |
| 17 | respectively, in any locale? |
| 18 | |
| 19 | Ulrich |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability | "René Neumann" <lists@××××××.eu> |
| Re: [gentoo-dev] [RFC] ban use of base-4 casemods in ebuilds due to locale collation instability | Mike Frysinger <vapier@g.o> |