1 |
On Sat, Jun 23, 2012 at 9:17 AM, Ciaran McCreesh |
2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
3 |
> On Sat, 23 Jun 2012 18:13:23 +0200 |
4 |
> Justin <jlec@g.o> wrote: |
5 |
>> Did you read what you wrote and thought about what you request from |
6 |
>> others? Probably you better should. |
7 |
> |
8 |
> Uh huh, and I think we all know there's a huge difference between |
9 |
> knowing what versions and slots are and knowing what "a multilib" is. |
10 |
> |
11 |
>> An example: |
12 |
>> |
13 |
>> "...slots and versions to "mean" something other than what they used |
14 |
>> to,..." |
15 |
>> |
16 |
>> is completely useless without a description of what SLOTS are about |
17 |
>> and how the should be used. And what is the wrong usage you can find; |
18 |
>> examples are necessary here for understanding. |
19 |
> |
20 |
> That's covered in the devmanual and in the user documentation, so |
21 |
> there's no need to repeat it here. |
22 |
|
23 |
http://devmanual.gentoo.org/general-concepts/slotting/index.html |
24 |
http://devmanual.gentoo.org/general-concepts/dependencies/index.html#slot-dependencies |
25 |
|
26 |
I don't think the documentation forbids what these developers are |
27 |
doing. I think you implemented a nice heuristic for your users in your |
28 |
resolver that used to work because slots had a typical set of users |
29 |
cases and the heuristic performed well in those cases. |
30 |
|
31 |
Now people are occasionally using slots in a different way and your |
32 |
heuristic penalizes those cases. That sucks, but you might have to |
33 |
actually change your resolver because I don't think 'funky-slots' |
34 |
properties is going to garner much adoption. It just appears that the |
35 |
heuristic you used to use isn't helpful anymore (or has too any false |
36 |
positives, or whatever.) |
37 |
|
38 |
-A |
39 |
|
40 |
> |
41 |
>> To me, it doesn't solve the root cause, but actually I can't judge |
42 |
>> this, because I am missing a description of what is really going |
43 |
>> wrong. |
44 |
> |
45 |
> As I've already said, this isn't about solving the root cause. It's |
46 |
> about reducing the impact of damage that's already been done until the |
47 |
> root cause is solved properly. |
48 |
> |
49 |
> -- |
50 |
> Ciaran McCreesh |