1 |
Marc Hildebrand <zypher <at> gentoo.org> writes: |
2 |
|
3 |
> > What do you think? LC_ALL=C in portage or not? |
4 |
> > |
5 |
> > - Stefan |
6 |
> |
7 |
> Well this problem (localized error messages) exists since I know linux |
8 |
> and the solution has always been "use per user locale settings and keep |
9 |
> LC_ALL=POSIX or =C as a system default". |
10 |
> Maybe we should just update the docs? |
11 |
|
12 |
A bug regarding this issue has been filled: |
13 |
http://bugs.gentoo.org/show_bug.cgi?id=134032 |
14 |
|
15 |
>From the current state of portage code, the patch in question while useful is |
16 |
not necessary. Portage already defines in /usr/lib/portage/portage_const.py: |
17 |
|
18 |
USER_CONFIG_PATH = "/etc/portage" |
19 |
EBUILD_SH_ENV_FILE = USER_CONFIG_PATH+"/bashrc" |
20 |
|
21 |
which is then used in /usr/lib/pym/portage.py: |
22 |
|
23 |
mysettings["PORTAGE_BASHRC"] = EBUILD_SH_ENV_FILE |
24 |
|
25 |
and consequently in /usr/lib/bin/ebuild.sh: |
26 |
|
27 |
if [ -f "${PORTAGE_BASHRC}" ]; then |
28 |
source "${PORTAGE_BASHRC}" |
29 |
fi |
30 |
|
31 |
So, if the documentation is updated (and possibly advertized in next GWN), no |
32 |
change (even small) is necessary. |
33 |
|
34 |
And while I can voice my (user's) opinion, I *really* like the idea of forcing |
35 |
the sane emerge environment by this one-liner. So in fact I'm torn apart... |
36 |
|
37 |
Wiktor Wandachowicz |
38 |
(SirYes) |
39 |
|
40 |
|
41 |
-- |
42 |
gentoo-dev@g.o mailing list |