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