1 |
On Mon, Oct 17, 2016 at 12:23 AM, Michał Górny <mgorny@g.o> wrote: |
2 |
|
3 |
> Hello, everyone. |
4 |
> |
5 |
> I'd like to point out a major problem in Gentoo: there's a fair number |
6 |
> of developers who add various local workarounds to problems they meet |
7 |
> and don't bother to report a bug. Worst than that, this applies not |
8 |
> only for upstream problems but also to Gentoo eclass/ebuild-related |
9 |
> issues. |
10 |
> |
11 |
> |
12 |
> Example: udev people had problems with MULTILIB_WRAPPED_HEADERS |
13 |
> in the past. Instead of contacting me (which would result in helpful |
14 |
> explanation how to do things properly), they abused bash to disable |
15 |
> the check function implicitly in the ebuilds. |
16 |
> |
17 |
> Nobody bothered to inform me of the issue there. Instead, I had to |
18 |
> notice it looking at the udev ebuilds accidentally. Furthermore, in |
19 |
> most of the ebuilds the workaround was no longer necessary but nobody |
20 |
> bothered to check that. |
21 |
> |
22 |
> |
23 |
> Example 2: Coacher had problem with git-r3 not trying fallback URIs |
24 |
> when earlier URI was https and https wasn't supported in git. So he |
25 |
> reordered URIs to have https last. With tiny explanation in some random |
26 |
> commit message. |
27 |
> |
28 |
> So we have a problem that affects around a half of git-r3 packages |
29 |
> (using quick grep, results inaccurate), however minor it is. Worse, it |
30 |
> affects the policy of preferring https and causes some people to reject |
31 |
> the policy silently. And nobody gives a damn to report it! |
32 |
> |
33 |
> |
34 |
> Therefore, I'd like to request establishing an official policy against |
35 |
> workarounds with no associated bug reports. |
36 |
> |
37 |
> Your thoughts? |
38 |
> |
39 |
> -- |
40 |
> Best regards, |
41 |
> Michał Górny |
42 |
> <http://dev.gentoo.org/~mgorny/> |
43 |
> |
44 |
|
45 |
+1. |
46 |
|
47 |
Anything serious enough to require a workaround or an upstream deviation |
48 |
should be documented in a bug report. |
49 |
|
50 |
And may also be something we should poke upstream about anyway. If junk |
51 |
hits us in gentoo, it may have come from upstream and may affect users |
52 |
outside of gentoo. |