Gentoo Archives: gentoo-user

From: William Kenworthy <billk@×××××××××.au>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: Reinstall + switch to KDE
Date: Thu, 20 Sep 2012 23:24:55
Message-Id: 1348183348.23652.1.camel@moriah
In Reply to: Re: [gentoo-user] Re: Reinstall + switch to KDE by Alan McKinnon
1 On Thu, 2012-09-20 at 18:20 +0200, Alan McKinnon wrote:
2 > On Thu, 20 Sep 2012 07:44:13 +0200
3 > Daniel Wagener <stelf@×××.net> wrote:
4 >
5 > > On Mon, 10 Sep 2012 14:44:33 -0500
6 > > Canek Peláez Valdés <caneko@×××××.com> wrote:
7 > >
8 > > > On Mon, Sep 10, 2012 at 2:36 PM, Alan McKinnon
9 > > > <alan.mckinnon@×××××.com> wrote:
10 > > > > On Mon, 10 Sep 2012 12:53:41 -0400
11 > > > > Andrey Moshbear <andrey.vul@×××××.com> wrote:
12 > > > >
13 > > > >> On Mon, Sep 10, 2012 at 12:43 PM, Nikos Chantziaras
14 > > > >> <realnc@×××××.com> wrote:
15 > > > >> > On 10/09/12 19:12, Samuraiii wrote:
16 > > > >> >>
17 > > > >> >> Hello,
18 > > > >> >> because I broke me PC and I need to reinstall it I'm going
19 > > > >> >> ask what should I preserve to make install faster:
20 > > > >> >
21 > > > >> > So what *is* broken? The hardware? If you have a new PC, you
22 > > > >> > simply need to transfer your Gentoo install to a new hard disk
23 > > > >> > using rsync.
24 > > > >>
25 > > > >> He borked his /usr/include due to an improperly-written
26 > > > >> uninstall rule in a Makefile.
27 > > > >>
28 > > > >
29 > > > > if "emerge -e world" runs, it will fix that little oopsie
30 > > >
31 > > > No, it won't; if enough files from /usr/include are gone/borked,
32 > > > most packages will fail compilation. glibc alone has ~450 files
33 > > > under /usr/include; and basically everything depends on glibc.
34 > >
35 > > hmm, my approach in that case would be to get /usr from a recent
36 > > stage3 tarball and then running emerge -e world
37 > >
38 > > but maybe there is a reason why nobody came up with that already :-/
39 > >
40 >
41 > But that would be too easy, no wonder no-one mentioned it :-)
42 >
43 > It probably is the right thing to do though. You don;t actually know
44 > every package that's affected, and no easy way to find out and no way
45 > to find false negatives.
46 >
47 ...
48
49 "equery check <pkgname>"
50
51 BillK