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