1 |
On 13:32 Thu 14 Apr , Kfir Lavi wrote: |
2 |
> When i run world update, I usually don't really check all the written |
3 |
> stuff. |
4 |
> |
5 |
> If I do this, I'm sure a lot more Gentoo users do the same. So do |
6 |
> expect people rebooting the machine without checking what your have |
7 |
> wrote. This can be a major headache if you have few systems that are |
8 |
> doing auto updates. I would solve this issue by stopping the emerge |
9 |
> and getting the attention of the user. If I don't get the attention of |
10 |
> the user, no openrc will be installed. It should be something like |
11 |
> emerge -C ... 1 .2 3 4 5... |
12 |
> |
13 |
> To conclude, you can't issue such a change without proper confirmation from |
14 |
> the user. |
15 |
|
16 |
I know this is the case. You're going to get literally thousands of |
17 |
people (or more) who break their Gentoo systems if that indeed is the |
18 |
consequence of not reading the migration guide and doing some action. |
19 |
|
20 |
From a glance over the guide, it wasn't immediately obvious what in |
21 |
there would result in a broken system. Perhaps it's the "run |
22 |
dispatch-conf" that's buried in the middle of a paragraph without enough |
23 |
emphasis? That's particularly confusing for people who use etc-update |
24 |
instead, and it *needs* to move somewhere more obvious like a separate |
25 |
code listing with big <important> tags and bold text. The line of red |
26 |
text just isn't enough, it needs to stand out even more. |
27 |
|
28 |
It seems like nobody's really clear on what exactly happens though, |
29 |
since I've seen people talking about this *maybe* resulting in an |
30 |
unbootable system. Has anyone tested it? |
31 |
|
32 |
One potential cleaner approach to the same idea Kfir suggested is to |
33 |
make it an interactive emerge with an ACCEPT_LICENSE-like feature that |
34 |
pops up something you must read and agree to. |
35 |
|
36 |
-- |
37 |
Thanks, |
38 |
Donnie |
39 |
|
40 |
Donnie Berkholz |
41 |
Sr. Developer, Gentoo Linux |
42 |
Blog: http://dberkholz.com |