public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chromium bloat
Date: Sat, 27 Feb 2016 17:44:03 +0000	[thread overview]
Message-ID: <3555732.tlsRSKLIFf@wstn> (raw)
In-Reply-To: <56D1CBB3.2030004@gmail.com>

On Saturday 27 February 2016 08:15:47 Daniel Frey wrote:
--->8
> The brackets mean the USE flag is forced, masked or removed.
> 
> (if you want to jump to the section in `man emerge` search for () using
> "/\(\)" as searching for verbose or -v shows results everywhere)

Actually, that search string failed in /usr/bin/most here, which I have as 
my MANPAGER. I just needed "/()".

> man emerge:
> 
>        --verbose [ y | n ] (-v short option)
>               Tell  emerge  to run in verbose mode.  Currently this flag
> causes emerge to print out GNU info errors, if any, and to show the USE
> flags that will be used for each package when pretending. The following
> symbols are affixed to USE
>               flags in order to indicate their status:
> 
>               Symbol   Location    Meaning
>              
> ──────────────────────────────────────────────────────────────
> 
>               -        prefix      not enabled (either disabled or
> removed) *        suffix      transition to or from the enabled state %  
>      suffix      newly added or removed
>               ()       circumfix   forced, masked, or removed
>               {}       circumfix   state is bound to FEATURES settings

So it is - thanks. I wonder how I missed it the first time. Anno Domini is at 
work again.

-- 
Rgds
Peter



      reply	other threads:[~2016-02-27 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 11:35 [gentoo-user] Chromium bloat Peter Humphrey
2016-02-27 12:51 ` Neil Bothwick
2016-02-27 14:58   ` Peter Humphrey
2016-02-27 15:18     ` Peter Humphrey
2016-02-27 16:15       ` Daniel Frey
2016-02-27 17:44         ` Peter Humphrey [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=3555732.tlsRSKLIFf@wstn \
    --to=peter@prh.myzen.co.uk \
    --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