| 1 |
On Sat, 25 Feb 2006 13:34:28 -0600 "Boyd Stephen Smith Jr." |
| 2 |
<bss03@××××××××××.com> wrote: |
| 3 |
| > | > ~arch means a package is a candidate for going into arch after |
| 4 |
| > | > further testing, if said testing does not turn up new bugs. This |
| 5 |
| > | > means that both the ebuild *and* the package should be likely |
| 6 |
| > | > to be stable. |
| 7 |
| > | |
| 8 |
| > | So, betas shouldn't ever be ~arch? Or is your definition of |
| 9 |
| > | stable broad enough to include betas? |
| 10 |
| > |
| 11 |
| > Entirely dependent on the upstream. I've had Vim beta releases in |
| 12 |
| > ~arch, for example, because I'm confident in upstream's ability to |
| 13 |
| > do beta releases without screwing up. |
| 14 |
| |
| 15 |
| So, it's based on the collective opinion of the gentoo developers? |
| 16 |
| Wouldn't it be better to put that in the hands of the gentoo user? |
| 17 |
|
| 18 |
Absolutely not. If there's one thing we've established over the years, |
| 19 |
it's that the vast majority of our users don't have the slightest clue |
| 20 |
what's best for them in terms of package stability. |
| 21 |
|
| 22 |
-- |
| 23 |
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) |
| 24 |
Mail : ciaranm at gentoo.org |
| 25 |
Web : http://dev.gentoo.org/~ciaranm |
Archives