On Thu, 20 Sep 2012 07:44:13 +0200 Daniel Wagener <st...@gmx.net> wrote:
> On Mon, 10 Sep 2012 14:44:33 -0500 > Canek Peláez Valdés <can...@gmail.com> wrote: > > > On Mon, Sep 10, 2012 at 2:36 PM, Alan McKinnon > > <alan.mckin...@gmail.com> wrote: > > > On Mon, 10 Sep 2012 12:53:41 -0400 > > > Andrey Moshbear <andrey....@gmail.com> wrote: > > > > > >> On Mon, Sep 10, 2012 at 12:43 PM, Nikos Chantziaras > > >> <rea...@gmail.com> wrote: > > >> > On 10/09/12 19:12, Samuraiii wrote: > > >> >> > > >> >> Hello, > > >> >> because I broke me PC and I need to reinstall it I'm going > > >> >> ask what should I preserve to make install faster: > > >> > > > >> > So what *is* broken? The hardware? If you have a new PC, you > > >> > simply need to transfer your Gentoo install to a new hard disk > > >> > using rsync. > > >> > > >> He borked his /usr/include due to an improperly-written > > >> uninstall rule in a Makefile. > > >> > > > > > > if "emerge -e world" runs, it will fix that little oopsie > > > > No, it won't; if enough files from /usr/include are gone/borked, > > most packages will fail compilation. glibc alone has ~450 files > > under /usr/include; and basically everything depends on glibc. > > hmm, my approach in that case would be to get /usr from a recent > stage3 tarball and then running emerge -e world > > but maybe there is a reason why nobody came up with that already :-/ > But that would be too easy, no wonder no-one mentioned it :-) It probably is the right thing to do though. You don;t actually know every package that's affected, and no easy way to find out and no way to find false negatives. So the correct approach is to realize that a complete rebuild finishes in a reasonable time, and then do it. -- Alan McKinnon alan.mckin...@gmail.com
