| 1 |
Hello! |
| 2 |
|
| 3 |
So, I can't find any documentation about this; nor can I find a |
| 4 |
best-practices list. Can we add broken ebuilds in-tree as long as they |
| 5 |
are package.masked? automagic deps, wrong deps, missing deps, file |
| 6 |
collisions, etc etc? Even if it makes the ebuild completely unusable |
| 7 |
by itself? |
| 8 |
|
| 9 |
If yes: |
| 10 |
|
| 11 |
So we can add completely broken and useless stuff to tree as long as |
| 12 |
it's package.masked? |
| 13 |
|
| 14 |
If no: |
| 15 |
|
| 16 |
What's the minimum amount of "working-ness" that an ebuild must have |
| 17 |
to be added to tree? Who decides this? The QA team? |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
~Nirbheek Chauhan |
| 22 |
|
| 23 |
Gentoo GNOME+Mozilla Team |
Archives