1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Richard Fish wrote: |
5 |
|
6 |
> env-update.sh outputs this message with a simple "echo", so no output |
7 |
> to stdout here. However portage writes most ">>>" messages to stderr. |
8 |
|
9 |
Well and good, but this is not an abnormal message, and there's no |
10 |
reason for it to go to stderr. stderr is for errors, else it's just |
11 |
unbuffered stdout, which isn't terribly helpful. |
12 |
|
13 |
File descriptor gymnastics and text munging should not be required in |
14 |
order to separate expected output from abnormal conditions. I expect |
15 |
that from Microsoft. ;-) |
16 |
|
17 |
> You can either file a bug report on bugs.gentoo.org to try and get the |
18 |
> behavior changed, |
19 |
|
20 |
Thank you, I'll look into that. Obviously, I was merely venting here. |
21 |
|
22 |
Cheers -d |
23 |
|
24 |
- -- |
25 |
David Talkington |
26 |
|
27 |
PGP key: http://www.prairienet.org/~dtalk/004B8F8B.asc |
28 |
-----BEGIN PGP SIGNATURE----- |
29 |
Version: GnuPG v1.4.5 (GNU/Linux) |
30 |
|
31 |
iD8DBQFFXLLA5FKhdwBLj4sRAr9eAJkBO7D7empiwxkA7+MriXL4tkx5sQCfaZXV |
32 |
8rPuON/F03fbU5SCuxFrucQ= |
33 |
=3WNZ |
34 |
-----END PGP SIGNATURE----- |
35 |
-- |
36 |
gentoo-user@g.o mailing list |