| 1 |
On Mon, 17 Oct 2016 09:23:09 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> Therefore, I'd like to request establishing an official policy against |
| 5 |
> workarounds with no associated bug reports. |
| 6 |
> |
| 7 |
> Your thoughts? |
| 8 |
|
| 9 |
Obviously I assume this is still a "to taste" thing, because when |
| 10 |
you're packaging something, and you find something upstream have done |
| 11 |
which makes sense for them, but not for gentoo, you're inclined to go |
| 12 |
"oh, right", and just side-step that, without such thought as to file a |
| 13 |
bug in the process. |
| 14 |
|
| 15 |
So obviously not *all* workarounds can have useful bugs filed for them. |
| 16 |
|
| 17 |
Unless I'm supposed to see the bug before I ship the code, and file a |
| 18 |
bug in gentoo, ship the ebuild with the workaround, and then close the |
| 19 |
bug, even though the bug never existed from any users perspective. |
| 20 |
|
| 21 |
So its just a matter of more clearly defining the scopes of workarounds |
| 22 |
were talking about here. |
Archives