1 |
>>>>> On Sun, 09 Jul 2017, Michał Górny wrote: |
2 |
|
3 |
> On nie, 2017-07-09 at 09:22 +0200, Ulrich Mueller wrote: |
4 |
>> Second, and more important, introduction of an automatic solver |
5 |
>> would inevitably lead to proliferation of REQUIRED_USE in the tree. |
6 |
>> However, nothing would guarantee that the package manager on the |
7 |
>> user's side is capable of solving the constraints automatically. |
8 |
>> The result would be more emerge failures and asking for more |
9 |
>> micro-management of flags by users. |
10 |
|
11 |
> Think of dynamic deps. We were able to eventually contain them, and |
12 |
> teach developers not to account for them even though they are still |
13 |
> enabled by default, I think. |
14 |
|
15 |
> I don't see why optional autosolving of REQUIRED_USE could not be |
16 |
> contained by a policy as well. |
17 |
|
18 |
Then can you please confirm that the policy outlined in |
19 |
https://devmanual.gentoo.org/general-concepts/use-flags/index.html#conflicting-use-flags |
20 |
can stay in place indefinitely, and that your GLEP doesn't intend to |
21 |
change it? |
22 |
|
23 |
> Of course, there will be some people who will violate it but it's |
24 |
> not something that doesn't happen anyway right now. |
25 |
|
26 |
A policy that isn't enforced is useless. |
27 |
|
28 |
> Are you suggesting that we introduce half-tested feature in EAPI 7, |
29 |
> then spend a few years figuring out that it doesn't work as |
30 |
> expected? |
31 |
|
32 |
No, I am suggesting that we introduce a new package manager feature in |
33 |
a well defined way, so that ebuild authors can rely on it. We have a |
34 |
mechanism for that, and I don't see a good reason not to follow it. |
35 |
|
36 |
> Because I don't see how we get it tested properly without having |
37 |
> users actually test it and report the results. |
38 |
|
39 |
It shouldn't be necessary for the spec to specify all details of the |
40 |
algorithm. It should catch the basics though in the next EAPI, like |
41 |
leftmost preferred, banning empty groups, and banning USE conditionals |
42 |
inside groups. |
43 |
|
44 |
Ulrich |