| 1 |
> |
| 2 |
> STABLE arch: |
| 3 |
> Obvious realy, stable packages only. Considered a stable ebuild and |
| 4 |
> stable software. |
| 5 |
|
| 6 |
"arch" |
| 7 |
|
| 8 |
> |
| 9 |
> PRESTABLE (perhaps called Testing?) ~arch: |
| 10 |
> Only software considered stable but whos ebuild is considered unstable |
| 11 |
> or just badly written. OpenOffice is a good example: 1.1 is a stable |
| 12 |
> release but the ebuild contains warnings about the ebuild itself being |
| 13 |
> alpha. |
| 14 |
|
| 15 |
"~arch" |
| 16 |
|
| 17 |
> |
| 18 |
> UNSTABLE >arch (or some other symbol): |
| 19 |
> Software stability takes precedence over ebuild stability here, eg a |
| 20 |
> package whos ebuild was very small and perfectly writen but the software |
| 21 |
> itself was considered unstable would be marked unstable and not |
| 22 |
> prestable. |
| 23 |
|
| 24 |
-> package.mask |
| 25 |
|
| 26 |
|
| 27 |
http://www.gentoo.org/doc/en/policy.xml explains this too: |
| 28 |
|
| 29 |
"Package.mask is used to prevent merging of packages that are broken, |
| 30 |
break something else, or badly need testing before going into ~ARCH |
| 31 |
KEYWORDS in the tree." |
| 32 |
|
| 33 |
"The purpose of ~arch is for testing new packages added to Portage." |
| 34 |
|
| 35 |
"When a package version has proved stable for sufficient time and the |
| 36 |
Gentoo maintainer of the package is confident that the upgrade will not |
| 37 |
break a regular Gentoo user's machine, then it can be moved from ~ARCH |
| 38 |
to ARCH." |
| 39 |
|
| 40 |
|
| 41 |
Just my $0.02 :-) |
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
.". |
| 46 |
/V\ [web ] http://0x1337.net | Behind every great |
| 47 |
// \\ [pgp ] http://0x1337.net/0x1337-pgp.txt | computer sits a |
| 48 |
/( )\ [geek] http://0x1337.net/0x1337-geek.txt | skinny, little geek. |
| 49 |
^'~'^ |
| 50 |
|
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-dev@g.o mailing list |
Archives