1 |
Krzysztof Pawlik wrote: |
2 |
> I've fixed few packages, and... leesten carefully... I'm going to say |
3 |
this only |
4 |
> once: next person to commit an ebuild with KEYWORDS="" (or KEYWORDS="-*") will |
5 |
> be punished... Alistair will send an e-mail every 10 minutes until the ebuild |
6 |
> gets proper keywords and ends up in package.mask. |
7 |
> |
8 |
|
9 |
Oh shit |
10 |
|
11 |
/me runs back to reverse all the commits in which I dropped all |
12 |
keywords. ;) |
13 |
|
14 |
On a more serious note. |
15 |
|
16 |
KEYWORDS="-*" is bad!!! and if I see anymore of it an email every 10 |
17 |
minutes will be the last of anyones problems. |
18 |
|
19 |
but im not that concerned about KEYWORDS="" |
20 |
|
21 |
I dropped keywords on a few packages in java-overlay because there deps |
22 |
weren't satisfied within gentoo or java-overlay ( I didn't check |
23 |
java-experimental unless it was obvious to me. aka hibernate-annotations |
24 |
). Eventually there will be an email going around with a list of ebuilds |
25 |
that have no keywords. These will either be junkyarded or moved to |
26 |
java-experimental (if that satisfies them). |
27 |
|
28 |
> Can we get commit hook that does some basic QA and aborts the commit if there |
29 |
> are QA errors (and some warning)? |
30 |
|
31 |
I will look into this at some point. I suppose there are many things we |
32 |
could do to help maintain qa. I suppose we also need more overview of |
33 |
our contributors. So I might attempt to generate reports, etc of |
34 |
commits by those users. |