Duncan wrote:
>
> Looking at the broader picture, the problem of extraneous packages in the 
> world file has always concerned me.  If it were to be done over again, 
> and I think Zac would likely agree, emerge would use --oneshot by 
> default, so as not to contaminate the world file unnecessarily.  Then 
> there'd be a different option (say -2) to add the package to the world 
> file if that's what was actually intended.
>
> That's actually how I have my emerge front-end scriptlets/aliases setup 
> here.  -1 is the default; if I want it in the world file I use the *2 
> script variant, which omits the -1.
>
> But of course changing behavior in mid-stream doesn't work so well, so 
> emerge continues to stick stuff in the world file by default.
>

I added -1 to my make.conf a long time ago.  Whenever I emerge something
and want it in the world file, just use the --select option.  If I
already emerged something but then want to add it to the world file,
just add the -n option too.  That keeps the world file clean and I can
test things before adding anything to the world file. 

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"