| 1 |
On 24/01/2013 09:46, Dale wrote: |
| 2 |
> Neil Bothwick wrote: |
| 3 |
>> On Thu, 24 Jan 2013 03:17:06 -0600, Dale wrote: |
| 4 |
|
| 5 |
<snip> |
| 6 |
|
| 7 |
> Why do you say that -N will compile packages that don't need it? If a |
| 8 |
> USE flags is added, changed or whatever, I want that change to be seen |
| 9 |
> and the package to be recompiled. It could very well affect how the |
| 10 |
> package works or some feature. |
| 11 |
|
| 12 |
There are various situations in which it can indeed be a waste of time. |
| 13 |
For example, running emerge -auDN @world prompts me to rebuild gcc: |
| 14 |
|
| 15 |
[ebuild R ] sys-devel/gcc-4.6.3 USE="(-go%)" |
| 16 |
|
| 17 |
Why? Because the toolchain eclass was recently modified to better |
| 18 |
support the Go programming language. But wait! I didn't have the "go" |
| 19 |
flag enabled before because it didn't exist. Nor will it be enabled in |
| 20 |
the prospective rebuild. What's more, I couldn't enable it even if I |
| 21 |
wanted to because it's masked for this version of gcc (as indicated by |
| 22 |
the parentheses). |
| 23 |
|
| 24 |
The upshot is that rebuilding gcc now would serve absolutely no purpose. |
| 25 |
The --changed-use parameter understands this whereas -N does not. |
| 26 |
|
| 27 |
Cheers, |
| 28 |
|
| 29 |
--Kerin |
Archives