| 1 |
On Thu, Sep 6, 2012 at 1:03 PM, Michael Orlitzky <michael@××××××××.com> wrote: |
| 2 |
> If there's really no reason, why would anyone bother to file a bug for |
| 3 |
> it? It's better for developers than the must-bump policy, and better for |
| 4 |
> users than what we have now. |
| 5 |
|
| 6 |
What change is even being proposed? If there is an issue that |
| 7 |
actually impacts users, then that issue is the bug, and bumping the |
| 8 |
EAPI is just the solution to the bug. |
| 9 |
|
| 10 |
If an ebuild unnecessarily ignores CFLAGS, or if it is a blocker to |
| 11 |
some eclass update, or whatever, then that is already considered a |
| 12 |
valid bug. |
| 13 |
|
| 14 |
That is my main concern with all of this stuff - just state what you |
| 15 |
need in terms of outcomes, not solutions. If you can't identify the |
| 16 |
outcome, then there is no need for the change anyway. By all means |
| 17 |
suggest solutions in the report, but don't confuse the solution with |
| 18 |
the problem. |
| 19 |
|
| 20 |
Rich |
Archives