On Wed, Oct 29, 2008 at 7:03 PM, Andrey Vul <[EMAIL PROTECTED]> wrote: >> >> Good digging around :). So this is a python bug then? Or does portage need >> to be update for some change that went into python? Actually, is this really >> even a bug...its just a minor cosmetic problem really. >> > One's bug is another's feature. > libc in uname is honestly WTF but this begs the real question: why > doesn't portage (emerge and repoman to be specific) simply get the > output of uname -a ? It's not written in C, you don't have to mess > around with 5-6 fd's to get the needed data. > > And I think that this is both a design bug and a red herring. > > By the way, should I make a bug report with a patch to remove this issue? > Making it selectable via FEATURES requires more digging around in portage. > -- > Andrey Vul
Dear Andrey & Andrey, thanks for the good info & ideas :) For the record, my uname -a is: Linux e6600 2.6.27-gentoo-r1 #1 SMP PREEMPT Thu Oct 23 17:45:32 CDT 2008 x86_64 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux Compared to that line from emerge --info: System uname: [EMAIL PROTECTED] Regards, Paul
