1 |
On Tue, Jun 23, 2009 at 5:33 PM, Nikos Chantziaras<realnc@×××××.de> wrote: |
2 |
> On 06/24/2009 03:27 AM, Mark Knecht wrote: |
3 |
>> |
4 |
>> Gentoo is for me. Gentoo is the only distro I run and the only one |
5 |
>> I've run for at least 6 years. Gentoo has run on THIS VERY MACHINE for |
6 |
>> over 4 years and it is the ONLY distro that has EVER run on this |
7 |
>> machine. Today I run eix-sync and emerge xorg-x11 and the machine |
8 |
>> breaks and I cannot go back. It is not my choice that Gentoo |
9 |
>> maintainers decided to drop something from portage required to make |
10 |
>> this machine run and not give me a way to get it back. Portage chose |
11 |
>> to erase files on MY machine - files that are required to make the |
12 |
>> machine work. Gentoo package maintainers decided to obsolete my |
13 |
>> machine, not me. |
14 |
> |
15 |
> You should have taken a backup of /usr/portage and created binary packages |
16 |
> using "quickpgk" before the update. Portage can't contain every ancient |
17 |
> version of every package out there. It would grow to infinity. Old stuff |
18 |
> has to go. That's the very nature of Gentoo's "rolling release" nature (or |
19 |
> on other words, its lack of a "stable" notion.) |
20 |
|
21 |
I have NEVER asked portage to keep a copy of EVERYTHING online. I |
22 |
think it's a sinthat portage decides to remove files from MY machine, |
23 |
files that I'm currently using, files that I require. |
24 |
|
25 |
Sure, easy to blame it on me with Gentoo. quickpkg might have been a |
26 |
solution if I'd known about it, so it's my fault. It's certainly not |
27 |
the fault of the designers of portage who could have checked to ensure |
28 |
that I had a binary package before they removed my files, or could |
29 |
have required an extra override at the command line to simply inform |
30 |
me they were going to take away MY files. No, I'm sure they don't care |
31 |
if they break machines. It's easy to chuckle in private instead of |
32 |
making a system that can go backward one step on this machine. One |
33 |
step, that's all. But yes, it's my fault. |
34 |
|
35 |
> |
36 |
> Anyway, see my other post, maybe you can go on with the update and have it |
37 |
> working in the end. |
38 |
> |
39 |
|
40 |
Yes, I read that. Thanks. |
41 |
|
42 |
> |
43 |
>> I'm sure there's some way to get things back working again but I don't |
44 |
>> know what they are. |
45 |
> |
46 |
> The rule is simple. If a fresh installation of Gentoo wouldn't work, you're |
47 |
> out of luck. Gentoo lacks releases. Either you change hardware or |
48 |
> distribution. |
49 |
> |
50 |
|
51 |
There is no way for me to know that any other distribution will fix |
52 |
this short of trying them. that's just not practical. |
53 |
|
54 |
- Mark |