On Thu, 27 Feb 2003 23:21:30 -0800
Matt Tucker <[EMAIL PROTECTED]> wrote:
> -- Susie <[EMAIL PROTECTED]> spake thusly:
>
> > I just rebuilt mine... Use "emerge -ep world && emerge -e world &&
>
> Just out of curiosity, what's the point of this? If emerge -ep world
> is going to fail, so is emerge -e world. And if you want to check what
> it's going to do before it starts doing it, why would you string one
> right after the other?
>
Actually that is the exact command I used(and I can tell you it
certainly didn't fail). 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.
>From the man page:
--emptytree (-e)
Virtually tweaks the tree of installed packages to only
contain
glibc; this is great to use together with --pretend. This
allows
developers to get a complete overview of the complete
dependency
tree of a package, and it enables complete trees to be
rebuilt
using the latest libraries.
--
Susie
VE7 HFA
[EMAIL PROTECTED]
http://arienadean.tripod.com/
-----------------------------------------------------------------------
"Failure is not falling down, it is not gettnig up again." - Mary
Pickford
--
[EMAIL PROTECTED] mailing list
