| 1 |
Duncan wrote: |
| 2 |
> |
| 3 |
> Looking at the broader picture, the problem of extraneous packages in the |
| 4 |
> world file has always concerned me. If it were to be done over again, |
| 5 |
> and I think Zac would likely agree, emerge would use --oneshot by |
| 6 |
> default, so as not to contaminate the world file unnecessarily. Then |
| 7 |
> there'd be a different option (say -2) to add the package to the world |
| 8 |
> file if that's what was actually intended. |
| 9 |
> |
| 10 |
> That's actually how I have my emerge front-end scriptlets/aliases setup |
| 11 |
> here. -1 is the default; if I want it in the world file I use the *2 |
| 12 |
> script variant, which omits the -1. |
| 13 |
> |
| 14 |
> But of course changing behavior in mid-stream doesn't work so well, so |
| 15 |
> emerge continues to stick stuff in the world file by default. |
| 16 |
> |
| 17 |
|
| 18 |
I added -1 to my make.conf a long time ago. Whenever I emerge something |
| 19 |
and want it in the world file, just use the --select option. If I |
| 20 |
already emerged something but then want to add it to the world file, |
| 21 |
just add the -n option too. That keeps the world file clean and I can |
| 22 |
test things before adding anything to the world file. |
| 23 |
|
| 24 |
Dale |
| 25 |
|
| 26 |
:-) :-) |
| 27 |
|
| 28 |
-- |
| 29 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
| 30 |
|
| 31 |
Miss the compile output? Hint: |
| 32 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives