From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage option "--changed-use" not working?
Date: Thu, 19 Jan 2012 19:12:54 -0800 [thread overview]
Message-ID: <CAE1pOi2nwyeCpszQKz6CdWAmK5jp_WqNXDjTqKxRmt4XEH74CA@mail.gmail.com> (raw)
In-Reply-To: <4F18C57A.1020701@gmail.com>
On 19 January 2012 17:38, Dale <rdalek1967@gmail.com> wrote:
> Hilco Wijbenga wrote:
>> On 19 January 2012 16:05, Dale <rdalek1967@gmail.com> wrote:
>>> Well, the USE flag got changed. Isn't that what -N is supposed to do?
>>
>> -N == --newuse not --changed-use :-)
>>
>> It's exactly for this reason that I use --changed-use and not
>> --newuse. See the man page for the details.
>>
>>
>
>
> Well, sort of seems like about the same. The dev changed the USE flag,
> it is changed, portage sees it was changed, portage wants to recompile
> it with the new/changed flags.
>
> I'm not exactly clear on the difference between newuse and changed-use.
> If you enable a USE flag, it is changed. If you disable a USE flag, it
> is changed. If a new flag comes along and it is different than the last
> install, then it can be either a new flag or a changed flag. It should
> recompile either way.
The point here is that a USE flag was removed but it wasn't enabled
anyway. So no recompile necessary. Which is what --changed-use is
supposed to be for (as I understand the man page).
> Maybe there is some subtle difference somewhere that I am missing.
Which is why I included what it says in the man page and then referred
you to said man page... ;-)
next prev parent reply other threads:[~2012-01-20 3:14 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 [this message]
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=CAE1pOi2nwyeCpszQKz6CdWAmK5jp_WqNXDjTqKxRmt4XEH74CA@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