1 |
Hilco Wijbenga wrote: |
2 |
> On 19 January 2012 19:25, Dale <rdalek1967@×××××.com> wrote: |
3 |
>> Hilco Wijbenga wrote: |
4 |
>>> On 19 January 2012 17:38, Dale <rdalek1967@×××××.com> wrote: |
5 |
>>>> Hilco Wijbenga wrote: |
6 |
>>>>> On 19 January 2012 16:05, Dale <rdalek1967@×××××.com> wrote: |
7 |
>>>>>> Well, the USE flag got changed. Isn't that what -N is supposed to do? |
8 |
>>>>> |
9 |
>>>>> -N == --newuse not --changed-use :-) |
10 |
>>>>> |
11 |
>>>>> It's exactly for this reason that I use --changed-use and not |
12 |
>>>>> --newuse. See the man page for the details. |
13 |
>>>>> |
14 |
>>>>> |
15 |
>>>> |
16 |
>>>> |
17 |
>>>> Well, sort of seems like about the same. The dev changed the USE flag, |
18 |
>>>> it is changed, portage sees it was changed, portage wants to recompile |
19 |
>>>> it with the new/changed flags. |
20 |
>>>> |
21 |
>>>> I'm not exactly clear on the difference between newuse and changed-use. |
22 |
>>>> If you enable a USE flag, it is changed. If you disable a USE flag, it |
23 |
>>>> is changed. If a new flag comes along and it is different than the last |
24 |
>>>> install, then it can be either a new flag or a changed flag. It should |
25 |
>>>> recompile either way. |
26 |
>>> |
27 |
>>> The point here is that a USE flag was removed but it wasn't enabled |
28 |
>>> anyway. So no recompile necessary. Which is what --changed-use is |
29 |
>>> supposed to be for (as I understand the man page). |
30 |
>>> |
31 |
>>>> Maybe there is some subtle difference somewhere that I am missing. |
32 |
>>> |
33 |
>>> Which is why I included what it says in the man page and then referred |
34 |
>>> you to said man page... ;-) |
35 |
>>> |
36 |
>>> |
37 |
>> |
38 |
>> |
39 |
>> Well, when I did mine, it showed up as a change. It was in yellow. |
40 |
>> Maybe your system was different or something. |
41 |
> |
42 |
> Nope, same here. And obviously there was a change: a flag was removed. |
43 |
> But, again, my understanding of --changed-use (as opposed to --newuse) |
44 |
> is that it should have prevented the reinstall. |
45 |
> |
46 |
>> Most man pages are Greek. My Greek is not real good. |
47 |
> |
48 |
> :-) I don't think they're quite that bad although I agree that you |
49 |
> sometimes sort of already need to know where to look. |
50 |
> |
51 |
> |
52 |
|
53 |
|
54 |
Sometimes my problem is it is like shooting skeet, it's a moving target. |
55 |
Sometimes it moves pretty darn fast too. Zac adds it faster than I can |
56 |
keep up. I wish they would announce new stuff when it get released, |
57 |
both unstable and stable. Then again, maybe it moves so fast he can't |
58 |
keep up either. lol |
59 |
|
60 |
Dale |
61 |
|
62 |
:-) :-) |
63 |
|
64 |
-- |
65 |
I am only responsible for what I said ... Not for what you understood or |
66 |
how you interpreted my words! |
67 |
|
68 |
Miss the compile output? Hint: |
69 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |