-- Susie <[EMAIL PROTECTED]> spake thusly: > Actually that is the exact command I used(and I can tell you it > certainly didn't fail).
I wasn't saying that it'd fail, I was saying that the "command && command" construct is used so that if the first command fails, the second command doesn't get run. You might use it for something like "cp <source> <dest> && gzip <source>" so that if the copy failed, the file wouldn't get gzipped. So to do it for "emerge -p && emerge", you're saying "pretend to emerge and if that succeeds, really emerge". > I wasn't aware at first of the -e switch bug and had had problems > with my world file. So I actually wanted to see what it was build so > I had it pretend. Then after that I did have it rebuild the whole > thing using "emerge -e world" and after that usually it wants you to > run etc-update to deal with globals.make, etc. Then finally after > I'd done that I ran the rebuildworld which is the script as mentioned > that rebuilds the world file that gets messed up from runing the > emerge with the -e switch. My point is that doing emerge -p <something> && emerge <something> is useless. 'emerge -p' gives you the same initial output as emerge, it just doesn't keep going. And if you want to check output before starting the merge, I would think you'd want longer than a 0-second pause. Put another way, you're saying "show me what you're going to do and then show me what you're going to do and then do it". It just seems weird to me. Maybe the confusion here is that I'm reading what you did as a single command, but you actually executed two or three separate commands. -- [EMAIL PROTECTED] mailing list
