1 |
Hilco Wijbenga wrote: |
2 |
> On 19 January 2012 17:38, Dale <rdalek1967@×××××.com> wrote: |
3 |
>> Hilco Wijbenga wrote: |
4 |
>>> On 19 January 2012 16:05, Dale <rdalek1967@×××××.com> wrote: |
5 |
>>>> Well, the USE flag got changed. Isn't that what -N is supposed to do? |
6 |
>>> |
7 |
>>> -N == --newuse not --changed-use :-) |
8 |
>>> |
9 |
>>> It's exactly for this reason that I use --changed-use and not |
10 |
>>> --newuse. See the man page for the details. |
11 |
>>> |
12 |
>>> |
13 |
>> |
14 |
>> |
15 |
>> Well, sort of seems like about the same. The dev changed the USE flag, |
16 |
>> it is changed, portage sees it was changed, portage wants to recompile |
17 |
>> it with the new/changed flags. |
18 |
>> |
19 |
>> I'm not exactly clear on the difference between newuse and changed-use. |
20 |
>> If you enable a USE flag, it is changed. If you disable a USE flag, it |
21 |
>> is changed. If a new flag comes along and it is different than the last |
22 |
>> install, then it can be either a new flag or a changed flag. It should |
23 |
>> recompile either way. |
24 |
> |
25 |
> The point here is that a USE flag was removed but it wasn't enabled |
26 |
> anyway. So no recompile necessary. Which is what --changed-use is |
27 |
> supposed to be for (as I understand the man page). |
28 |
> |
29 |
>> Maybe there is some subtle difference somewhere that I am missing. |
30 |
> |
31 |
> Which is why I included what it says in the man page and then referred |
32 |
> you to said man page... ;-) |
33 |
> |
34 |
> |
35 |
|
36 |
|
37 |
Well, when I did mine, it showed up as a change. It was in yellow. |
38 |
Maybe your system was different or something. |
39 |
|
40 |
Most man pages are Greek. My Greek is not real good. |
41 |
|
42 |
Dale |
43 |
|
44 |
:-) :-) |
45 |
|
46 |
-- |
47 |
I am only responsible for what I said ... Not for what you understood or |
48 |
how you interpreted my words! |
49 |
|
50 |
Miss the compile output? Hint: |
51 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |