public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Harry Putnam <reader@newsguy.com>
Subject: Re: [gentoo-user]  Can I get a tip for reading eix output?
Date: Mon, 15 Jun 2009 16:22:27 +0200	[thread overview]
Message-ID: <200906151622.27246.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <87zlc9n0jl.fsf@newsguy.com>

On Monday 15 June 2009 14:28:46 Harry Putnam wrote:
> Can I get a likely search string for the massive man page of eix to
> understand all the info contained in its ouput.

eix's man page always seemed to me to break rule #1 of user-interfaces:

"Do not expose the underlying implementation in the interface."

> A quick search on `output' seems to miss it.

You want to search on "\!t" in this case

> Things like found in this output:
>
> eix ^apr$
>
> * dev-libs/apr
>      Available versions:  (1)  1.2.11!t (~)1.2.12!t (~)1.3.0!t 1.3.2!t
> 1.3.3!t 1.3.5!t {debug doc ipv6 urandom}
>      Homepage:            http://apr.apache.org/
>      Description:         Apache Portable Runtime Library
>
>
> What do the `!t' entries following the versions available mean?

RESTRICT="test"

You can find a clue in sub-section "Slots" under main heading "OUTPUT"

> Also, is it odd to have older versions under `~'?

No, it just means the maintainer didn't change anything in the older unstable 
versions when marking the later one stable.

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2009-06-15 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 12:28 [gentoo-user] Can I get a tip for reading eix output? Harry Putnam
2009-06-15 14:22 ` Alan McKinnon [this message]
2009-06-16 12:46   ` bn
2009-06-16 15:42     ` Alan McKinnon
2009-06-16 19:28       ` Mike Edenfield
2009-06-16 19:55         ` bn
2009-06-15 14:59 ` Mike Edenfield

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=200906151622.27246.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=reader@newsguy.com \
    /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