1 |
On 2009-01-01, Matt Causey <matt.causey@×××××.com> wrote: |
2 |
|
3 |
> I am total Gentoo newb :D but it seems kind of fundamental to |
4 |
> the concept of this distribution that its users are going to |
5 |
> make themselves aware of the details of system updates. Short |
6 |
> of reading ridiculous amounts of doco...folks should be |
7 |
> reading the output of the emerge commands to learn about edge |
8 |
> cases like this one. |
9 |
|
10 |
There are plenty of ebuilds that when they know they are going |
11 |
to break the system will abort with a warning to the user how |
12 |
to either prevent the breakage or how to force the install. I |
13 |
don't see any reason why the nvidia ebuild should go ahead |
14 |
and break the system and then tell you about it afterwards. |
15 |
|
16 |
Why not tell you about how the update will break your system |
17 |
and then _not_ doing the update? |
18 |
|
19 |
> Personally, I rather like this approach. The folks |
20 |
> maintaining the builds take the time to identify these edge |
21 |
> cases, which makes the portage text output quite helpful. |
22 |
|
23 |
It would be even more helpful if the ebuild _doesn't_ break |
24 |
your system. |
25 |
|
26 |
-- |
27 |
Grant |