1 |
For any who any may be interested, after filing two bug reports, the |
2 |
problems regarding python-updater and eselect are solved. |
3 |
|
4 |
My ~/.bashrc file, which bash will read whenever it is invoked by |
5 |
a script such as eselect or python-updater, contained the following line: |
6 |
|
7 |
set -o posix |
8 |
|
9 |
This directive insures that only code that is posix compliant will |
10 |
operate correctly. By removing the line, both eselect and python- |
11 |
updater can operate normally without modification. |
12 |
|
13 |
But a larger, more philosophical, issue is still unsettled. Why does |
14 |
Gentoo allow non-posix compliant code? I have been using my .bashrc |
15 |
file for many years without any problem whatsoever. Only after moving |
16 |
to Gentoo just a few months ago do these problems surface. |
17 |
|
18 |
There is no right answer. Conformance is a matter of taste and preference, |
19 |
but standards also exist for good reasons. Standards are supposed to insure |
20 |
that code operates as intended irrespective of the system or environment. |
21 |
In this case, a lack of attention to standards has caused a little grief. |
22 |
|
23 |
Anyway, that's my rant. I've learned a little more and that's always a good |
24 |
thing. Time really hasn't been wasted because others may experience a similar |
25 |
problem in the future and will now have some reference. |
26 |
|
27 |
Frank Peters |