Hilco Wijbenga wrote:
> On 19 January 2012 19:25, Dale <rdalek1...@gmail.com> wrote:
>> Hilco Wijbenga wrote:
>>> On 19 January 2012 17:38, Dale <rdalek1...@gmail.com> wrote:
>>>> Hilco Wijbenga wrote:
>>>>> On 19 January 2012 16:05, Dale <rdalek1...@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... ;-)
>>>
>>>
>>
>>
>> Well, when I did mine, it showed up as a change.  It was in yellow.
>> Maybe your system was different or something.
> 
> Nope, same here. And obviously there was a change: a flag was removed.
> But, again, my understanding of --changed-use (as opposed to --newuse)
> is that it should have prevented the reinstall.
> 
>> Most man pages are Greek.  My Greek is not real good.
> 
> :-) I don't think they're quite that bad although I agree that you
> sometimes sort of already need to know where to look.
> 
> 


Sometimes my problem is it is like shooting skeet, it's a moving target.
 Sometimes it moves pretty darn fast too.  Zac adds it faster than I can
keep up.  I wish they would announce new stuff when it get released,
both unstable and stable.  Then again, maybe it moves so fast he can't
keep up either.  lol

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"

Reply via email to