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. Most man pages are Greek. My Greek is not real good. 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"
