1 |
Markos Chandras posted on Sat, 14 Aug 2010 20:00:40 +0300 as excerpted: |
2 |
|
3 |
> Cause I don't like users to compile the same damn package over and over. |
4 |
> -r1 for docs on ${PF}, -r2 for CFLGAS, -r3 for LDFLAGS, -r4 for ... Is |
5 |
> that a good reason or not? It is not like I introduce huge patches with |
6 |
> bugfixes etc. My fixes are QA fixes not *serious* bugfixes anyway. |
7 |
> Furthermore the QA fixes I do ( CC,CFLAGS,LDFLAGS ) are easily spotted |
8 |
> and there isn't much for users to test anyway. Either you respect the |
9 |
> bloody flags or not. I don't do blindly commits. I try to test the |
10 |
> packages in multiple chroots anyway. |
11 |
|
12 |
User perspective here... |
13 |
|
14 |
For LDFLAGS, given the new --as-needed default, I'd prefer the rev-bump. |
15 |
Yes, it requires a rebuild, but the rebuilds will occur as the bugs are |
16 |
fixed so it's a few at a time for people who keep reasonably updated |
17 |
(every month or more frequently). The alternative is triggering a several- |
18 |
hundred-package rebuild when some base library package updates, because |
19 |
all those LDFLAGS respecting changes weren't rev-bumped and the user's |
20 |
installed set is still ignoring them, and thus --as-needed. |
21 |
|
22 |
Better the few at a time, even if some of them end up being bumped and |
23 |
built twice as a result, than the multiple hundred at once. |
24 |
|
25 |
So I'm not going to get into who's right or wrong vs. current policy, but |
26 |
that's my perspective as a user. For LDFLAGS respecting changes at least, |
27 |
please do the rev-bumps, as the cost of failing to do so, thus triggering |
28 |
a mass update when a base lib changes, far exceeds that of dealing with |
29 |
them on a trickle-in basis, even if a few do end up updated twice as a |
30 |
result. |
31 |
|
32 |
Thanks. =:^) |
33 |
|
34 |
-- |
35 |
Duncan - List replies preferred. No HTML msgs. |
36 |
"Every nonfree program has a lord, a master -- |
37 |
and if you use the program, he is your master." Richard Stallman |