Dark Templar wrote: > When I reinstalled gcc and glibc, migrating from non-multilib amd64 arch > to multilib one, I just unpacked gentoo stage3 into temporary directory, > chrooted there, made binary packages out of installed ones (quickpkg > <name>), copied resulted binary packages and their metadata to host > system (i.e. moved $chroot/usr/portage/packages into > /usr/portage/packages) and installed those binary packages replacing > current ones. It's fast (you don't have to build packages from scratch), > and it didn't fail me even once, although I heard playing with glibc > such way may be dangerous (particularly, downgrading it). I guess it > works for other purposes too. > > I don't like installing from scratch if there is a way to fix it. I > don't like that approach 'unpack stage on top of your system', because > it will lead to system pollution: a lot of files might be no longer > tracked by package manager after that. > > But that's just my experience and opinion. I hope it can help you. > >
If I can install something as a binary and then get a clean emerge -e system/world out of it, I think it would be OK. Thing is, I'm concerned something is amiss with the stage3 tarball. If that is the case, I want to inform the person that overseas that so it can be fixed. Installing Gentoo is hard enough for someone seasoned but would be a nightmare for someone new to Gentoo. Now to figure out what is the root problem on this thing. Dale :-) :-)
