1 |
Michael Jones wrote: |
2 |
> |
3 |
> My reason for replying initially was that I didn't think it was fair |
4 |
> to make light of users who don't expect to *need* to scrutinize the |
5 |
> output of emerge every single time they run it. Those people exist |
6 |
> (hi, nice to meet you), and it's not fair to say they're wrong or |
7 |
> somehow making a grave error in judgement. |
8 |
> |
9 |
> It's entirely fair to say that they are treading on thin ice, and that |
10 |
> if they choose to do this they should understand the risks, but it's |
11 |
> not fair to say they're automatically wrong to use the tool in a way |
12 |
> that the tool allows itself to be used. |
13 |
> |
14 |
> Either way, we don't need to turn this into a long and in depth |
15 |
> discussion, so I probably won't reply to the list again unless you |
16 |
> have any specific questions or concerns for me. |
17 |
|
18 |
Thank you for the reasonable response. |
19 |
|
20 |
Dale, of course, has spewed hate at me for simply trying to make my life |
21 |
as convenient as possible while still using Gentoo over here without |
22 |
even providing a satisfactory answer as to why. |
23 |
|
24 |
|
25 |
My experience with Emerge is that it goes out of it's way to be obscure |
26 |
and conceales huge amounts of information from the user by default, like |
27 |
all unix programs, and must be coaxed with a litany of flags, |
28 |
parameters, and environment variables to produce any useful output at |
29 |
all. Whenever it's output pattern changes I need to go do research to |
30 |
re-enable whatever it decided to hide this month. |
31 |
|
32 |
At this point, I need to update about 25% of my system, or on the order |
33 |
of 460 packages. Going through this list manually simply is not feasible |
34 |
or even productive. Having tried several approaches to starting the |
35 |
update including emerge --update system, emerge --update world, and |
36 |
emerge --update packageX, I have decided that the only command that will |
37 |
sucessfully update my system in it's present state is emerge --emptytree |
38 |
world . The singular obstacle to that working appears to be the absence |
39 |
of those patch files. |
40 |
|
41 |
Now, back to the problem at hand. |
42 |
|
43 |
Since 2004, I have been using "emerge --sync" to update my portage tree. |
44 |
I understand that it accesses a local list of mirrors and then runs |
45 |
rsync against one of those. On spinning media hard disks it is helpful |
46 |
to pre-cache the portage tree as shown in my scripts, on SSD systems, it |
47 |
is simply harmless. I refreshed my mirror list and selected either HTTP |
48 |
or RSYNC mirrors from across the USA. |
49 |
|
50 |
The problem is NOT with emerge in that the files that it complains about |
51 |
not being present are in fact not present. I tried to find them on |
52 |
google and only found changelogs, not the actual files in a downloadable |
53 |
state that I can add manually. I am still angry with Emerge for not |
54 |
updating all packages for which those files are not required or even |
55 |
compiling packages until it encounters one for which it does not have |
56 |
the files. |
57 |
|
58 |
I prefer to obey the server's admonition against updating more than once |
59 |
a day, however this is an emergency and I have run sync against it maybe |
60 |
a dozen times. I have no reason to expect that there is any discrepency |
61 |
between the files I have and what's actually on the servers unless there |
62 |
is an entirely different set of servers out there which actually do have |
63 |
the files I need or a completely new and different way to sync them, |
64 |
(WTF IS Eix? ) . =| |
65 |
|
66 |
-- |
67 |
Please report bounces from this address to atg@×××××××××.com |
68 |
|
69 |
Powers are not rights. |