1 |
On Tue, 29 Sep 2015 20:45:10 +0200, lee wrote: |
2 |
|
3 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
4 |
> |
5 |
> > Patches are always more welcome than suggestions. "Fix it!" is never |
6 |
> > as welcome as "here's how". I think it was Canek who said "code |
7 |
> > talks". |
8 |
> |
9 |
> Do you have an example for such a case? |
10 |
|
11 |
Just look at b.g.o. Many bug reports include a patch submitted by a user |
12 |
that makes its way into the tree. |
13 |
|
14 |
> My experience has disproved |
15 |
> this claim, and I've even seen people fixing stuff multiple times after |
16 |
> I told them it's broken and provided a perfectly working version before |
17 |
> telling them, much better coded, which they could have used instead of |
18 |
> insisting on their crappy code and trying to fix it several times. |
19 |
|
20 |
You cannot judge one group of people on the behaviour of an unrelated |
21 |
group. |
22 |
|
23 |
> >> and now even if you |
24 |
> >> came up with some pointer what to look at (since emerge, for |
25 |
> >> example, is a wrapper script from which I couldn't see where to |
26 |
> >> start), |
27 |
> > |
28 |
> > Really? The first few lines of the script tell you where the real |
29 |
> > scripts are? The wrapper seems to be there to deal with different |
30 |
> > default Python versions. |
31 |
> |
32 |
> Yes, really. I don't know python and I can see that emerge points to |
33 |
> some library directory while I can not see which script would actually |
34 |
> run other than the wrapper. |
35 |
|
36 |
#!/usr/lib/python-exec/python-exec2-c |
37 |
# vim:fileencoding=utf-8:ft=python |
38 |
# (c) 2012 Michał Górny |
39 |
# Released under the terms of the 2-clause BSD license. |
40 |
# |
41 |
# This is not the script you are looking for. This is just a wrapper. |
42 |
# The actual scripts of this application were installed |
43 |
# in subdirectories of /usr/lib/python-exec. |
44 |
# You are most likely looking for one of those. |
45 |
|
46 |
In there you will find python2.7/emerge and python3.4/emerge (depending |
47 |
on which Python versions you have installed). |
48 |
|
49 |
> I don't believe that they let everyone modify what they're working on, |
50 |
> so they are the only ones who /can/ fix it. Besides, show me where I |
51 |
> said something like "I want the devs to fix it". |
52 |
|
53 |
They don't. You submit the modifications in the bug report and they vet |
54 |
and apply the patches. |
55 |
|
56 |
> > Adding the word "just" to a demand does not make the task any |
57 |
> > simpler, nor does it increase your chances of getting what you want. |
58 |
> |
59 |
> Go ahead and show me where I have demanded something. |
60 |
|
61 |
Your insistence that it should be changed amounts to a demand. Your |
62 |
assertion that it can be done easily only demeans the efforts of the |
63 |
devs, implying that the fix is simple but they cannot be bothered. |
64 |
|
65 |
> > On the contrary, it serves to illustrate that you do not grasp the |
66 |
> > complexity of the situation. |
67 |
> |
68 |
> Perhaps you can enlighten me how it is so difficult to change a message |
69 |
> from "slot conflict" to "slot conflict (can probably be ignored while |
70 |
> there are other problems)" and what the complexity is which makes it |
71 |
> impossible to do so. |
72 |
|
73 |
Changing the message is trivial, knowing when to change it is not. Unless |
74 |
you can provide a means to tell unimportant slot conflicts from important |
75 |
ones, Context is everything and the variety of Gentoo systems out there |
76 |
make it extremely difficult for portage to understand the context in |
77 |
human terms. |
78 |
|
79 |
|
80 |
-- |
81 |
Neil Bothwick |
82 |
|
83 |
Sometimes too much to drink is not enough. |