| 1 |
On 06/30/14 22:15, Jeroen Roovers wrote: |
| 2 |
> On Mon, 30 Jun 2014 09:25:27 -0400 |
| 3 |
> Rich Freeman <rich0@g.o> wrote: |
| 4 |
> |
| 5 |
>> Agree 100%. I'm taking about masking things that HAVEN'T BEEN TESTED |
| 6 |
>> AT ALL. The maintainer knows that they compile, and that is it. |
| 7 |
> |
| 8 |
> Developers who "HAVEN'T [...] TESTED AT ALL" and still commit their |
| 9 |
> changes to the tree should immediately hand in their toys and leave |
| 10 |
> the project. |
| 11 |
> |
| 12 |
|
| 13 |
I usually avoid overlays (best way to make things hard to find), so when |
| 14 |
there's stuff that upstream says is experimental (e.g. perl6/rakudo with |
| 15 |
the MoarVM backend) I have no issue with adding it as un-keyworded |
| 16 |
ebuilds to the tree. That way it's easy to test, and once there's a bit |
| 17 |
more confidence that it works well enough it's trivial to keyword. |
Archives