From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A question about emerge --info
Date: Wed, 29 Oct 2008 20:03:42 -0400 [thread overview]
Message-ID: <e38d12ff0810291703m2fa38c97ld7d3731e12bc85c4@mail.gmail.com> (raw)
In-Reply-To: <350fc7cf0810291657t20e74d6ag70b05bf8e23973ba@mail.gmail.com>
>
> 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
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
next prev parent reply other threads:[~2008-10-30 0:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 22:53 [gentoo-user] A question about emerge --info Paul Hartman
2008-10-29 23:06 ` Andrey Vul
2008-10-29 23:09 ` Andrey Falko
2008-10-29 23:13 ` Andrey Vul
2008-10-29 23:23 ` Andrey Falko
2008-10-29 23:32 ` Andrey Vul
2008-10-29 23:41 ` Andrey Vul
2008-10-29 23:51 ` Andrey Vul
2008-10-29 23:57 ` Andrey Falko
2008-10-30 0:03 ` Andrey Vul [this message]
2008-10-30 0:15 ` Andrey Falko
2008-10-30 0:26 ` Andrey Vul
2008-10-30 2:02 ` Andrey Vul
2008-10-30 10:37 ` Geralt
2008-10-30 1:49 ` Paul Hartman
2008-10-30 0:47 ` Joshua Murphy
2008-10-30 1:30 ` Andrey Vul
2008-10-30 1:31 ` Andrey Vul
2008-10-30 12:26 ` Albert Hopkins
2008-10-30 12:43 ` Heiko Wundram
2008-10-30 13:44 ` Albert Hopkins
2008-10-29 23:21 ` Paul Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e38d12ff0810291703m2fa38c97ld7d3731e12bc85c4@mail.gmail.com \
--to=andrey.vul@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox