1 |
On Sat, Sep 15, 2018 at 12:29 AM Fabian Groffen <grobian@g.o> wrote: |
2 |
> |
3 |
> On 15-09-2018 00:07:12 +0300, Alon Bar-Lev wrote: |
4 |
> > > |
5 |
> > > Perhaps, if one persists on going this route, only do this for platforms |
6 |
> > > that upstream supports, such that arches which will suffer from this |
7 |
> > > (typically ppc, sparc, ...) don't have to be blocked by this. |
8 |
> > |
9 |
> > Exactly in these cases the -Werror is useful as if upstream expects no |
10 |
> > warnings then any warning should block installation and trigger bug |
11 |
> > report. In Gentoo in many cases we use packages on platform has no |
12 |
> > access to, our feedback to upstream is valuable. A great example is |
13 |
> > gnutls in which we collectively (maintainer, unstable users, |
14 |
> > architecture teams, stable users) found issues on architectures that |
15 |
> > almost nobody other than Gentoo has access to. |
16 |
> > |
17 |
> |
18 |
> I don't believe Gentoo users are (supposed to be) an extension of |
19 |
> upstreams. |
20 |
|
21 |
This is exactly what I think that is special about Gentoo, and the |
22 |
reason I use Gentoo. Unlike other distribution Gentoo is the closest |
23 |
thing of using upstream. A maintainer in Gentoo who is not see himself |
24 |
part of the upstream packages he maintains has far less impact than a |
25 |
maintainer who does see himself as part of upstream or is upstream. |
26 |
|
27 |
Per your statement, we should not allow any architecture or setup that |
28 |
upstream, such as exact versioning, architecture or toolchain. |
29 |
|
30 |
> If upstreams insist on that, they should make their software |
31 |
> non-free, adding a non-modification clause or something. In any case, |
32 |
> it is not Gentoo's job IMHO. |
33 |
|
34 |
Then we cannot re-distribute or patch, how is it related to the |
35 |
discussion? We are talking about open source projects and I know it is |
36 |
cliche... the "greater good" and helping the "free open source |
37 |
movement" a a viable alternative. I thought this is what unite us |
38 |
here. |
39 |
|
40 |
> In the end it is Gentoo who needs to care |
41 |
> for its users. I prefer we do that by giving them an option to become |
42 |
> that extension of upstream, e.g. by USE=upstream-cflags, which Gentoo |
43 |
> disables by default. |
44 |
|
45 |
Do you think someone do not care about the users? Do you actually |
46 |
think upstream does not care about users? I do not understand this |
47 |
statement. If downstream maintainer believes that upstream is friendly |
48 |
for the Gentoo overhead (which is higher than binary distributions) or |
49 |
create the relationship in which Gentoo is 1st citizen at upstream, |
50 |
why do you think users cannot use vanilla upstream? |
51 |
|
52 |
> As maintainer and/or enthusiastic user, like you wrote for gnutls, I |
53 |
> would be more than happy to provide build logs/errors for all the arches |
54 |
> I have access to. So like I wrote before, I think we should consider |
55 |
> case-by-case basis to make it easy to do so. |
56 |
|
57 |
This entire discussion is to allow case-by-case and not black and |
58 |
white approach recently enforced. |
59 |
|
60 |
Regards, |
61 |
Alon |