public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Portage option "--changed-use" not working?
Date: Thu, 19 Jan 2012 13:44:22 -0800	[thread overview]
Message-ID: <CAE1pOi2PCZhEgbdqYbBhegrXtiQo6MXor-vPY63-ryPsqpyJHQ@mail.gmail.com> (raw)
In-Reply-To: <20120119153025.54e4e4c1@fuchsia.remarqs.net>

On 19 January 2012 13:30, »Q« <boxcars@gmx.net> wrote:
> On Wed, 18 Jan 2012 11:07:09 -0800
> Hilco Wijbenga <hilco.wijbenga@gmail.com> wrote:
>
>> In "man emerge" I read:
>>
>> --changed-use
>>   Tells  emerge  to  include  installed packages where USE flags have
>> changed since installation. This option also implies the --selective
>> option. Unlike --newuse, the --changed-use option does not trigger
>> reinstallation when flags that the user has not enabled are added or
>> removed.
>>
>> So I always include "--changed-use" when upgrading @world. But with
>> the removal of kdeenablefinal I now get 150 reinstalls with
>> changed-use. This seems to be contradicting the man page? Or am I
>> misunderstanding things? Or did I misconfigure something? To be clear,
>> I have never enabled kdeenablefinal.
>
> I don't have an answer -- this is just a "me too" post.  I see the same
> behavior.

Thank you. I was starting to feel lonely. :-)

In case you're interested, I managed to work around the 150
unnecessary reinstalls by removing all 'kdeenablefinal' references in
/var/db/pkg/*/*/IUSE. This seems to work very well but it may have
unintended side effects that I'm not aware of.



  reply	other threads:[~2012-01-19 21:45 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 [this message]
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«
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=CAE1pOi2PCZhEgbdqYbBhegrXtiQo6MXor-vPY63-ryPsqpyJHQ@mail.gmail.com \
    --to=hilco.wijbenga@gmail.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