1 |
On 04/26/2015 05:28 PM, Philip Webb wrote: |
2 |
> |
3 |
>> More seriously, once you start working on (3), you'll realize |
4 |
>> that just because the error msgs suck doesn't mean you can make them better. |
5 |
> |
6 |
> If they "suck", they're not worth issuing, are they ? |
7 |
> I'm not willing to become a dev, so I'll never know if I cd improve them, |
8 |
> but it doesn't follow that no-one else could. |
9 |
> |
10 |
|
11 |
They give you the information you need to update your question. |
12 |
|
13 |
You don't need to be a Gentoo developer to contribute to portage. They |
14 |
have a mailing list and all patches are posted there for review, Gentoo |
15 |
dev or not. |
16 |
|
17 |
|
18 |
>> If you're willing to wait an hour, it might be able to come up |
19 |
>> with a list of ways you could resolve a conflict, but basically |
20 |
>> all of them will be wrong, eg suggestion #1, uninstall everything. |
21 |
> |
22 |
> Really, this is a flippant response to a serious issue, |
23 |
> which is being raised more often on the Gentoo User list. |
24 |
> |
25 |
|
26 |
It wasn't meant that way -- I was trying to point out that this is one |
27 |
of those problems that sounds easy but turns out to be incredibly hard. |
28 |
|
29 |
Dependency resolution is already slow when it only takes your installed |
30 |
packages into account. It would take oh-so-much longer if you wanted to |
31 |
consider "what if" questions involving the entire tree. And most of the |
32 |
suggestions it would come up with are indeed ridiculous. Uninstalling a |
33 |
few things in @world will probably solve your conflict. Is that not a |
34 |
valid suggestion in some cases? Why not? Can you determine those cases |
35 |
automatically without input from the user? |
36 |
|
37 |
I'm not saying it can't be done, but it's deceptively hard to |
38 |
(automatically) come up with a list of non-ridiculous suggestions before |
39 |
the user in question dies of old age. Relevant xkcd: |
40 |
|
41 |
https://xkcd.com/1425/ |