| 1 |
I believe QA is important from the perspective that you want to assure that |
| 2 |
the ebuilds work. Nothing makes a casual user more annoyed that having an |
| 3 |
emerge for his machine fail to work. But if you are running the emerges |
| 4 |
unconstrained (e.g. you specify them in the keywords file) then you are |
| 5 |
"exposed". |
| 6 |
|
| 7 |
A recent example is the mythtv package. It does not compile on an x86 |
| 8 |
without significant intervention (Gentoo Bug #292421). How does it make it |
| 9 |
into the "release" category without it compiling on the most common |
| 10 |
machines? (I'm dealing with an older x86 Pentium IV Prescott machine from |
| 11 |
HP and there have to be millions of them out there in the world.). |
| 12 |
|
| 13 |
There should be some sort of QA procedure which says "the package builds on |
| 14 |
these minimal list of machines" before it should be released. |
| 15 |
|
| 16 |
Then there is a separate discussion about how to best migrate people from |
| 17 |
the "approved" packages to the cutting edge packages with some level of |
| 18 |
warning to the user ("this may be problematic") |
| 19 |
|
| 20 |
Robert |
Archives