public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage option "--changed-use" not working?
Date: Thu, 19 Jan 2012 16:28:15 -0600	[thread overview]
Message-ID: <4F1898FF.1070106@gmail.com> (raw)
In-Reply-To: <CAE1pOi1N_WQN=SBFe3rgM2hmRnd5R290ukW24vi7GDXo30Mh6w@mail.gmail.com>

Hilco Wijbenga wrote:
> Hi all,
> 
> 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.
> 
> The full command I usually run is
> 
> emerge --verbose --deep --with-bdeps=y --complete-graph --update
> --changed-use --keep-going world
> 
> should that be relevant.
> 
> Cheers,
> Hilco
> 
> 


Just to be clear, it was a dev that changed the kdeenablefinal flag.  It
was sort of discussed on -dev.  I think the dev that did it doesn't use
-N so it doesn't affect him and I guess he thinks it won't affect others
either.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"



  parent reply	other threads:[~2012-01-19 22:29 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 ` Dale [this message]
2012-01-19 23:01   ` [gentoo-user] " 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=4F1898FF.1070106@gmail.com \
    --to=rdalek1967@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