1 |
El mar, 05-06-2012 a las 08:44 -0400, Aaron W. Swenson escribió: |
2 |
[...] |
3 |
> "There's never anything important in all that text." - Anonymous |
4 |
> Gentoo User |
5 |
> |
6 |
> We've already determined that the users don't read the output. This is |
7 |
> a known fact. Something I repeat in #gentoo more often than I care to |
8 |
> admit is "Seriously, read the output." I agree with the users that |
9 |
> there's too much output, and some of the output is indeed useless. |
10 |
> |
11 |
> The output they aren't reading isn't just rebuild commands, but also |
12 |
> the next step they're supposed to take after the emerge has finished, |
13 |
> groups their users need to be in to use a particular feature, et cetera. |
14 |
> |
15 |
> The ideal solution is for the Ebuild to instruct the PMS to rebuild |
16 |
> the dependent packages. |
17 |
> |
18 |
> We can have a variable called REBUILD. All packages that would need to |
19 |
> be rebuilt can be listed in it. Only those packages that are installed |
20 |
> would be built. The actual list of the packages to be rebuilt would be |
21 |
> determined at dependency checking time. That way, the user can approve |
22 |
> the rebuild of the packages. |
23 |
|
24 |
We all know what would be the "ideal solution", the problem is how to |
25 |
implement it (and how many years we need to wait to get it working). |
26 |
|
27 |
> |
28 |
> Just placing the commands in a separate log won't really solve a whole |
29 |
> lot. Further, it will bump any elog messages even further down in the |
30 |
> importance ranking. |
31 |
> |
32 |
|
33 |
It will allow administrators to easily automate via scripts rebuilding |
34 |
of packages, allowing them to get system more solid after a big update. |
35 |
Also, currently I usually need to surf in big summary.log to directly |
36 |
find commands to rebuild things because most of elog messages are |
37 |
useless to me (a lot of them because they are always shown in every |
38 |
update and are useful only the first time you read them, other times you |
39 |
already remember, for example, how to setup e4rat). |
40 |
|
41 |
Current situation of breaking systems when people don't read summary.log |
42 |
JUST AFTER update completes won't help to force people to read them, |
43 |
will simply break their systems and give a really poor impression of |
44 |
Gentoo breaking easily when updating. Think, for example, on a lot of |
45 |
people that leaves system updating at night time, then, when he/she |
46 |
tries to use it next morning he sees some things are broken and need to |
47 |
be rebuilt. All that rebuilding work could be done during the same night |
48 |
but, due current way of handling things, he needs to have his system |
49 |
broken during more hours (when he needs to use it) until things are |
50 |
rebuilt. |