| 1 |
On Wed, Oct 29, 2008 at 7:03 PM, Andrey Vul <andrey.vul@×××××.com> wrote: |
| 2 |
>> |
| 3 |
>> Good digging around :). So this is a python bug then? Or does portage need |
| 4 |
>> to be update for some change that went into python? Actually, is this really |
| 5 |
>> even a bug...its just a minor cosmetic problem really. |
| 6 |
>> |
| 7 |
> One's bug is another's feature. |
| 8 |
> libc in uname is honestly WTF but this begs the real question: why |
| 9 |
> doesn't portage (emerge and repoman to be specific) simply get the |
| 10 |
> output of uname -a ? It's not written in C, you don't have to mess |
| 11 |
> around with 5-6 fd's to get the needed data. |
| 12 |
> |
| 13 |
> And I think that this is both a design bug and a red herring. |
| 14 |
> |
| 15 |
> By the way, should I make a bug report with a patch to remove this issue? |
| 16 |
> Making it selectable via FEATURES requires more digging around in portage. |
| 17 |
> -- |
| 18 |
> Andrey Vul |
| 19 |
|
| 20 |
Dear Andrey & Andrey, thanks for the good info & ideas :) |
| 21 |
|
| 22 |
For the record, my uname -a is: |
| 23 |
|
| 24 |
Linux e6600 2.6.27-gentoo-r1 #1 SMP PREEMPT Thu Oct 23 17:45:32 CDT |
| 25 |
2008 x86_64 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel |
| 26 |
GNU/Linux |
| 27 |
|
| 28 |
Compared to that line from emerge --info: |
| 29 |
|
| 30 |
System uname: Linux-2.6.27-gentoo-r1-x86_64-Intel-R-_Core-TM-2_CPU_6600_@_2.40GHz-with-glibc2.2.5 |
| 31 |
|
| 32 |
Regards, |
| 33 |
Paul |
Archives