1 |
On 17/10/16 03:23 AM, Michał Górny wrote: |
2 |
> Hello, everyone. |
3 |
> |
4 |
> I'd like to point out a major problem in Gentoo: there's a fair number |
5 |
> of developers who add various local workarounds to problems they meet |
6 |
> and don't bother to report a bug. Worst than that, this applies not |
7 |
> only for upstream problems but also to Gentoo eclass/ebuild-related |
8 |
> issues. |
9 |
> |
10 |
> |
11 |
> Example: udev people had problems with MULTILIB_WRAPPED_HEADERS |
12 |
> in the past. Instead of contacting me (which would result in helpful |
13 |
> explanation how to do things properly), they abused bash to disable |
14 |
> the check function implicitly in the ebuilds. |
15 |
> |
16 |
> Nobody bothered to inform me of the issue there. Instead, I had to |
17 |
> notice it looking at the udev ebuilds accidentally. Furthermore, in |
18 |
> most of the ebuilds the workaround was no longer necessary but nobody |
19 |
> bothered to check that. |
20 |
> |
21 |
> |
22 |
> Example 2: Coacher had problem with git-r3 not trying fallback URIs |
23 |
> when earlier URI was https and https wasn't supported in git. So he |
24 |
> reordered URIs to have https last. With tiny explanation in some random |
25 |
> commit message. |
26 |
> |
27 |
> So we have a problem that affects around a half of git-r3 packages |
28 |
> (using quick grep, results inaccurate), however minor it is. Worse, it |
29 |
> affects the policy of preferring https and causes some people to reject |
30 |
> the policy silently. And nobody gives a damn to report it! |
31 |
> |
32 |
> |
33 |
> Therefore, I'd like to request establishing an official policy against |
34 |
> workarounds with no associated bug reports. |
35 |
> |
36 |
> Your thoughts? |
37 |
> |
38 |
|
39 |
To be clear, are you referring here to workarounds only regarding |
40 |
gentoo related stuffs (use of eclasses, package manager (ie portage) |
41 |
functionality, etc) or are you also referring to the various |
42 |
workarounds we as maintainers need to do to say, the use of build |
43 |
tools (cmake, etc) or upstream's codebase/build system itself, to |
44 |
successfully package it as well? |