1 |
Alan Grimes wrote: |
2 |
> Mick wrote: |
3 |
>> Hello Mr Grimes, |
4 |
>> |
5 |
>> I see you still have trouble dealing with your rage issues. |
6 |
>> |
7 |
>> I recommend you seek professional help about that. |
8 |
>> Nah! Let the man vent. Gentoo is a particularly effective (meta)distro for |
9 |
>> this purpose too. It will invariably do *exactly* what you instruct it, |
10 |
>> although this comes with no guarantee this will be what wanted it to do. |
11 |
>> |
12 |
>> It forces you to learn through practice. ;-) |
13 |
> No, not in this case. |
14 |
> Emerge is clearly looking for any tenible excuse not to do anything |
15 |
> whatsoever, and will not do anything at all if any such excuse exists. |
16 |
> |
17 |
> Six months ago, it wasn't like this. It would generally plow ahead and |
18 |
> start compiling the shit you asked it to. This WOULD sometimes cause |
19 |
> problems, which could affect multi-user systems and server situations, |
20 |
> but on my desktop, all of these problems would go away by the end of the |
21 |
> update list and 95% of the time, revdep-rebuild wouldn't have anything |
22 |
> to do. |
23 |
> |
24 |
> And then some pinhead got an idea that you could verify the workingness |
25 |
> of every package by spending twenty minutes of cpu time examining |
26 |
> ebuilds.... |
27 |
> |
28 |
> This could work, (given 20 minutes) almost, if you set --backtrack=30. |
29 |
> However, not having this set by default is a wonderful opportunity to |
30 |
> annoy the crap out of the user and such opportunities are never to be |
31 |
> passed up. NEVER!! |
32 |
> |
33 |
|
34 |
|
35 |
I've mentioned this before. The reason you are running into all this is |
36 |
because of the update process YOU use. Because you chose to use a |
37 |
update process that several very experienced Gentoo users have told you |
38 |
will result in this sort of problem, you need to place the blame |
39 |
somewhere besides on Gentoo and emerge. |
40 |
|
41 |
Yea, emerge can have its bumps at times and do something unexpected, but |
42 |
in your case, it is not emerge that is causing the problem. If the |
43 |
problem was emerge, other people on this list would be running into the |
44 |
same problem you are. Gentoo updates do not work like Ubuntu or some |
45 |
other binary based distro. You will learn that or find yourself in the |
46 |
exact same mess you are in now until you do. How long that takes is up |
47 |
to you tho. |
48 |
|
49 |
Basically, take the advice from some people who have been doing this for |
50 |
years or continue along the path that you have proven doesn't work. |
51 |
When people like Alan McKinnon or Neil tell you that what you are doing |
52 |
isn't going to end well, it pays to listen. Heck, even I know better |
53 |
than to update my Gentoo box the way you do and I don't even try and |
54 |
claim to know as much as either of those two much less both put together. |
55 |
|
56 |
Might I also add, besides blaming emerge, why not post with some info |
57 |
that people can actually look at? As it is now, I don't think you have |
58 |
even posted what package you are having trouble with. I don't have ESP |
59 |
and I don't recall seeing anyone else on this list claiming they have it |
60 |
either. I can recall me blasting hal but one thing about it, people |
61 |
knew what problem I was having and what it was with. |
62 |
|
63 |
Dale |
64 |
|
65 |
:-) :-) |