From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Portage option "--changed-use" not working?
Date: Fri, 20 Jan 2012 10:53:32 -0600 [thread overview]
Message-ID: <20120120105332.6c2e6c2f@fuchsia.remarqs.net> (raw)
In-Reply-To: 4F18DEAB.4070003@gmail.com
On Thu, 19 Jan 2012 21:25:31 -0600
Dale <rdalek1967@gmail.com> wrote:
> Most man pages are Greek. My Greek is not real good.
Maybe you've got LINGUAS set incorrectly. ;)
Quoting the relevant bit again,
the --changed-use option does not trigger reinstallation when flags
that the user has not enabled are added or removed.
kdeenablefinla was a flag the user (me or Hilco) had *not* enabled, so
that option should *not* have triggered reinstallation.
FWIW, there is discussion of the issue of triggering needless
reinstalls on the dev list now because of kdeenablefinal, buried in the
thread "[gentoo-commits] gentoo-x86 commit in sys-libs/glibc:...". It's
mixed in with arguing about changing USE flags on stable ebuilds.
--changed-use isn't mentioned, instead --exclude=kde-base/* is
recommended, and they are talking about mentioning --exclude in the
--newuse section of the man page.
I'm not filing a --changed-use bug or posting in the dev list because of
Medico's IMO rather prickly attitude about this kind of thing. He
says in this case:
The fact is, the user is not being forced to rebuild anything. They can
simply run full system updates with --newuse less often if it puts
too much strain on them.
Lest I seem ungrateful, let me be clear I do appreciate the tons of
work he's put into portage for many years.
next prev parent reply other threads:[~2012-01-20 16:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 19:07 [gentoo-user] Portage option "--changed-use" not working? Hilco Wijbenga
2012-01-19 21:30 ` [gentoo-user] " »Q«
2012-01-19 21:44 ` Hilco Wijbenga
2012-01-19 22:28 ` [gentoo-user] " Dale
2012-01-19 23:01 ` Hilco Wijbenga
2012-01-20 0:05 ` Dale
2012-01-20 0:15 ` Hilco Wijbenga
2012-01-20 1:38 ` Dale
2012-01-20 3:12 ` Hilco Wijbenga
2012-01-20 3:25 ` Dale
2012-01-20 3:50 ` Hilco Wijbenga
2012-01-20 9:07 ` Dale
2012-01-20 9:27 ` Neil Bothwick
2012-01-20 10:08 ` Dale
2012-01-20 12:06 ` Neil Bothwick
2012-01-20 12:21 ` Dale
2012-01-20 17:00 ` [gentoo-user] " »Q«
2012-01-21 11:26 ` Alan McKinnon
2012-01-21 23:45 ` Hilco Wijbenga
2012-01-22 0:16 ` Alan McKinnon
2012-01-22 2:23 ` »Q«
2012-01-22 4:34 ` Walter Dnes
2012-01-22 6:07 ` »Q«
2012-01-22 7:48 ` Dale
2012-01-22 8:40 ` Alan McKinnon
2012-01-22 11:09 ` Neil Bothwick
2012-01-20 16:53 ` »Q« [this message]
2012-01-20 18:37 ` Dale
2012-01-20 18:39 ` »Q«
2012-01-20 20:52 ` [gentoo-user] " Dale
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=20120120105332.6c2e6c2f@fuchsia.remarqs.net \
--to=boxcars@gmx.net \
--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