| 1 |
On 15-09-2018 00:07:12 +0300, Alon Bar-Lev wrote: |
| 2 |
> > |
| 3 |
> > Perhaps, if one persists on going this route, only do this for platforms |
| 4 |
> > that upstream supports, such that arches which will suffer from this |
| 5 |
> > (typically ppc, sparc, ...) don't have to be blocked by this. |
| 6 |
> |
| 7 |
> Exactly in these cases the -Werror is useful as if upstream expects no |
| 8 |
> warnings then any warning should block installation and trigger bug |
| 9 |
> report. In Gentoo in many cases we use packages on platform has no |
| 10 |
> access to, our feedback to upstream is valuable. A great example is |
| 11 |
> gnutls in which we collectively (maintainer, unstable users, |
| 12 |
> architecture teams, stable users) found issues on architectures that |
| 13 |
> almost nobody other than Gentoo has access to. |
| 14 |
> |
| 15 |
|
| 16 |
I don't believe Gentoo users are (supposed to be) an extension of |
| 17 |
upstreams. If upstreams insist on that, they should make their software |
| 18 |
non-free, adding a non-modification clause or something. In any case, |
| 19 |
it is not Gentoo's job IMHO. In the end it is Gentoo who needs to care |
| 20 |
for its users. I prefer we do that by giving them an option to become |
| 21 |
that extension of upstream, e.g. by USE=upstream-cflags, which Gentoo |
| 22 |
disables by default. |
| 23 |
|
| 24 |
As maintainer and/or enthusiastic user, like you wrote for gnutls, I |
| 25 |
would be more than happy to provide build logs/errors for all the arches |
| 26 |
I have access to. So like I wrote before, I think we should consider |
| 27 |
case-by-case basis to make it easy to do so. |
| 28 |
|
| 29 |
Fabian |
| 30 |
|
| 31 |
-- |
| 32 |
Fabian Groffen |
| 33 |
Gentoo on a different level |
Archives