1 |
On Fri, 2007-09-21 at 04:23 +0000, Duncan wrote: |
2 |
> Just to point out... I've seen people mention overlaying a stage-3 on an |
3 |
> existing installation for recovery reasons, generally broken gcc or (on |
4 |
> amd64) switching back to multilib from 64-bit only profiles, so it |
5 |
> /cannot/ be rightly assumed that there's not an existing configuration |
6 |
> in /root/. (Whether that's the right way to accomplish such recovery |
7 |
> isn't the point; the point is, it's done, by people desperate to get a |
8 |
> working system once again who know no other way to do it.) |
9 |
|
10 |
Anyone doing anything like this deserves all the suck that comes with |
11 |
it. If some file gets overwritten on their system, so be it. It's not |
12 |
our job to hand hold when people are doing things that are pretty stupid |
13 |
to begin with when anyone with sense would be sure to --exclude things |
14 |
they know they won't want (like /root)... ;] |
15 |
|
16 |
> Chris's idea of testing both USE=build *AND* that there's no existing |
17 |
> file there that's going to get blown away, sounds reasonable, regardless |
18 |
> of the debate over where the code is eventually placed. |
19 |
|
20 |
Thanks, but if the maintainers don't want to do it, there's not much we |
21 |
can do about it. |
22 |
|
23 |
-- |
24 |
Chris Gianelloni |
25 |
Release Engineering Strategic Lead |
26 |
Alpha/AMD64/x86 Architecture Teams |
27 |
Games Developer/Council Member/Foundation Trustee |
28 |
Gentoo Foundation |