From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I update *every* ebuild?
Date: Wed, 23 Jan 2013 17:01:11 -0600 [thread overview]
Message-ID: <20130123230111.GP30998@server> (raw)
In-Reply-To: <20130123222754.44b4bc13@digimed.co.uk>
On Wed, Jan 23, 2013 at 10:27:54PM +0000, Neil Bothwick wrote:
> On Wed, 23 Jan 2013 15:21:35 -0600, Bruce Hill wrote:
>
> > N = newuse (pkgs with changed USE flags)
>
> --changed-use makes more sense than -N, it saves unnecessary compiling.
If I understand "man emerge", --newuse tells me if an installed package has a
USE flag that was added, removed, turned on, or turned off; whereas
--changed-use only notifies me if a USE flag that I've chosen on my installed
packages are changed -- not any other USE flags the maintainer, or some other
committer, has changed (those have bitten me in the past).
Since I'm not really interested in reading the ChangeLog for *hundreds* of
packages, N (--newuse) suits me better. Those flags have special colors and
one or more of - * % () symbols so a quick glance lets me know *which* pkgs
the dev has changed, and *which* pkgs ChangeLog I might want to read.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-01-23 23:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:48 [gentoo-user] How can I update *every* ebuild? Jarry
2013-01-23 19:52 ` Florian Philipp
2013-01-23 19:53 ` Michael Mol
2013-01-23 20:07 ` Hilco Wijbenga
2013-01-23 20:24 ` Michael Mol
2013-01-24 0:02 ` Dale
2013-01-23 21:21 ` Bruce Hill
2013-01-23 22:27 ` Neil Bothwick
2013-01-23 23:01 ` Bruce Hill [this message]
2013-01-23 23:15 ` Neil Bothwick
2013-01-23 23:37 ` Bruce Hill
2013-01-24 8:32 ` Neil Bothwick
2013-01-24 9:17 ` Dale
2013-01-24 9:27 ` Neil Bothwick
2013-01-24 9:46 ` Dale
2013-01-24 12:37 ` Neil Bothwick
2013-01-24 12:54 ` Jean-Christophe Bach
2013-01-24 13:38 ` Yohan Pereira
2013-01-24 14:04 ` Neil Bothwick
2013-01-24 12:43 ` Kerin Millar
2013-01-24 14:12 ` Trevor D. Manning
2013-01-24 18:17 ` [gentoo-user] " »Q«
2013-01-24 7:21 ` [gentoo-user] " Alan McKinnon
2013-01-24 12:59 ` Kerin Millar
2013-01-24 15:41 ` Stroller
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=20130123230111.GP30998@server \
--to=daddy@happypenguincomputers.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