From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Confusion with eix output
Date: Wed, 21 Apr 2010 16:11:59 -0400 [thread overview]
Message-ID: <4BCF5C0F.4070807@kutulu.org> (raw)
In-Reply-To: <201004211248.56610.jcunning@cunning.ods.org>
On 4/21/2010 3:48 PM, James Cunning wrote:
> I am having some trouble, I think, with my nvidia video driver, and eix
> produces some output I cannot decipher from information in the man page:
>
> jlc64 X11 # eix nvidia-drivers
> [D] x11-drivers/nvidia-drivers
> Available versions: [M]71.86.07!s [M]~71.86.09!s 96.43.09!s ~96.43.11!s
> 173.14.15!s ~173.14.18!s 180.29!s ~180.60!s {acpi custom-cflags gtk
> kernel_FreeBSD kernel_linux multilib userland_BSD}
> Installed versions: 190.42-r3!s(11:04:43 AM 04/21/2010)(acpi gtk
> kernel_linux multilib -custom-cflags)
> Homepage: http://www.nvidia.com/
> Description: NVIDIA X11 driver and GLX libraries
>
> The man page goes into great detail how to specify many things, but doesn't
> explain in simple terms the format of its default outputs. In particular, I
> don't understand what the [D] means, but would appreciate any clues to a more
> comprehensible explanation for all its output.
I feel your pain. The eix man page is a perfect example of why GNU made
the info system (which is otherwise overkill in most cases.)
At any rate: eix's output tries to mimic the emerge -v output when
possible. In this case, [D] means eix thinks your installed version is
higher than the latest unmasked version in the tree, and that you should
'D'owngrade. You could also see 'U', if eix thinks you need to upgrade.
You probably need to eix-update after your most recent sync. Use
eix-sync instead of emerge --sync if, like me, you tend to forget that step.
--Mike
prev parent reply other threads:[~2010-04-21 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 19:48 [gentoo-user] Confusion with eix output James Cunning
2010-04-21 20:11 ` Mike Edenfield [this message]
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=4BCF5C0F.4070807@kutulu.org \
--to=kutulu@kutulu.org \
--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