1 |
On Sat, Aug 14, 2010 at 08:21:15PM +0300, Alex Alexander wrote: |
2 |
> On Sat, Aug 14, 2010 at 08:00:40PM +0300, Markos Chandras wrote: |
3 |
> > On Sat, Aug 14, 2010 at 07:16:26PM +0300, Alex Alexander wrote: |
4 |
> > > Does respecting LDFLAGS change the installed files in any way? yes. |
5 |
> > > Will users benefit from your change if you don't revbump? No. |
6 |
> > > |
7 |
> > > I think that chain of logic is enough to warrant a revbump and it is |
8 |
> > > covered by the devmanual since the change affects the installed package. |
9 |
> > No it doesn't. If it was that clear we wouldn't debated over this over and |
10 |
> > over. The cvs logs and you will see that other devs are fixing the package |
11 |
> > without revbump. |
12 |
> |
13 |
> The fact that others do what you do doesn't automatically make it right. |
14 |
It means that there is something wrong with documentation |
15 |
> |
16 |
> > > |
17 |
> > > It's merely a cp, why are you making such a fuss about it? You're doing |
18 |
> > > a good job already, we're just pointing out ways to make it even better |
19 |
> > > |
20 |
> > Cause I don't like users to compile the same damn package over and over. -r1 |
21 |
> > for docs on ${PF}, -r2 for CFLGAS, -r3 for LDFLAGS, -r4 for ... Is that a good |
22 |
> > reason or not? It is not like I introduce huge patches with bugfixes etc. My |
23 |
> > fixes are QA fixes not *serious* bugfixes anyway. |
24 |
> > Furthermore the QA fixes I do ( CC,CFLAGS,LDFLAGS ) are easily spotted and |
25 |
> > there isn't much for users to test anyway. Either you respect the bloody flags |
26 |
> > or not. I don't do blindly commits. I try to test the packages in multiple |
27 |
> > chroots anyway. |
28 |
> |
29 |
> All your fixes are important else you wouldn't be doing them. |
30 |
> |
31 |
> I still don't understand why you don't want to revbump. |
32 |
Cause I already said that I consider my changes trivial so the only actual |
33 |
testing could be performed when the package is about to get stabilized |
34 |
> |
35 |
> Your changes may not affect program features but they do fix hidden |
36 |
> issues. Issues that might help users later (for example, rebuilding a |
37 |
> package with --as-needed may reduce revdep-rebuilds in the future). |
38 |
> |
39 |
> You can always try to reduce revbumps by doing all the things you |
40 |
> mentioned together, if possible. |
41 |
No cause I am not the maintainer so I fix whatever gets reported on bugzilla |
42 |
and assigned to QA. |
43 |
> |
44 |
> In any case, unless we're talking about openoffice or kdelibs, revbumps |
45 |
> don't really cost so much anymore. |
46 |
Not if you own a single core CPU |
47 |
> |
48 |
> > > :) |
49 |
> > > |
50 |
> > > BTW, archs do the final testing, but much testing is done by the users |
51 |
> > > themselves, who report the bugs that get fixed before the packages get a |
52 |
> > > STABLEREQ bug ;) |
53 |
> > Most of these bugs don't come from users but from Diego. Why? Because users |
54 |
> > don't bother reading the build.log and see if all their flags are respected or |
55 |
> > not. I wouldn't do it either. This |
56 |
> |
57 |
> I never said users report these specific bugs. But they will test *your* |
58 |
> revbumps and may report other problems you didn't hit. |
59 |
> |
60 |
> > > > > Please, don't skip revbumps to avoid "tree spamming", thats why we have |
61 |
> > > > > revbumps in the first place ;) |
62 |
> > I am not convinced yet that this kind of QA fixes require a revbump. As I |
63 |
> > said, commit an actual patch, assigned to QA and if the rest of the members |
64 |
> > agree on that I am willing to change my policy. |
65 |
> |
66 |
> Now you're just being stubborn. I'm pretty sure your mentor told you "any |
67 |
> change to installed files warrants a revbump" ;) |
68 |
Pretty sure this rule is not that strict. |
69 |
> |
70 |
> Do we really need bureaucracy to enforce a commonly followed but not |
71 |
> documented policy? |
72 |
So document this policy to point stubborn maintainers to it |
73 |
|
74 |
Apparently I pissed a lot people off so I will siege my QA fixes for now. |
75 |
Apparently I need a break |
76 |
> |
77 |
> > > > > > unless something is on stable branch, I fix it as it is. I don't want to |
78 |
> > > > > > version bump anything because I don't want to mess with anyones |
79 |
> > > > > > packages. I only do QA fixing. If you have problem touching your |
80 |
> > > > > > packages just say it |
81 |
> > > > > > > |
82 |
> > > > > > > A. |
83 |
> > > > > > > |
84 |
> > > > > > > [1] https://bugs.gentoo.org/show_bug.cgi?id=332523 |
85 |
> > > > > > |
86 |
> > > > > > -- |
87 |
> > > > > > Markos Chandras (hwoarang) |
88 |
> > > > > > Gentoo Linux Developer |
89 |
> > > > > > Web: http://hwoarang.silverarrow.org |
90 |
> > > > > |
91 |
> > > > > -- |
92 |
> > > > > Alex Alexander -=- wired |
93 |
> > > > > Gentoo Linux Developer -=- Council / Qt / KDE / more |
94 |
> > > > > www.linuxized.com |
95 |
> > > > |
96 |
> > > > |
97 |
> > > > |
98 |
> > > > -- |
99 |
> > > > Markos Chandras (hwoarang) |
100 |
> > > > Gentoo Linux Developer |
101 |
> > > > Web: http://hwoarang.silverarrow.org |
102 |
> > > > Key ID: 441AC410 |
103 |
> > > > Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410 |
104 |
> > > |
105 |
> > > |
106 |
> > > |
107 |
> > > -- |
108 |
> > > Alex Alexander -=- wired |
109 |
> > > Gentoo Linux Developer -=- Council / Qt / KDE / more |
110 |
> > > www.linuxized.com |
111 |
> > |
112 |
> > |
113 |
> > |
114 |
> > -- |
115 |
> > Markos Chandras (hwoarang) |
116 |
> > Gentoo Linux Developer |
117 |
> > Web: http://hwoarang.silverarrow.org |
118 |
> > Key ID: 441AC410 |
119 |
> > Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410 |
120 |
> |
121 |
> |
122 |
> |
123 |
> -- |
124 |
> Alex Alexander -=- wired |
125 |
> Gentoo Linux Developer -=- Council / Qt / KDE / more |
126 |
> www.linuxized.com |
127 |
|
128 |
|
129 |
|
130 |
-- |
131 |
Markos Chandras (hwoarang) |
132 |
Gentoo Linux Developer |
133 |
Web: http://hwoarang.silverarrow.org |
134 |
Key ID: 441AC410 |
135 |
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410 |