ColdWind wrote:maggu2810 wrote:I thought testing is keyword masked and unstable could be hard masked.
Is there an 'official' statement that determines the 'official' names?
AFAIK, hard masked ebuilds are not "unstable", they are "not supported for end-users". Debian's testing and unstable concepts doesn't apply to Gentoo. If you unmask all hard masked packages you won't get the equivalent to Debian's unstable... you'll get a screwed system.
Call ~arch testing or unstable (who cares?) but the set of package.mask'ed packages is not the unstable "branch".
Historically it's stable and unstable in gentoo, and hard masked are "known to break". Nowadays, with all the overlays, I'd call ~arch the equivalent of debian testing, and overlays the new unstable (hope I've got those the right way round.) Newer stuff tends to come in via overlays (unless it's based on a long-standing project, which might still be worked on in an unofficial overlay) where most of the interesting stuff happens if you follow the code; ~arch in that context is much more of a QA stage than it used to be.
This is prob'y why many think Gentoo's no longer bleeding-edge: ~arch used to be much more so than it is now, and people think it has to be in the main tree to count as Gentoo. That stuff now happens in overlays which are an excellent way to organise things imo, since you simply add the overlay for the area you're interested in (eg pro-audio or haskell) and there's usually an IRC room where you can feedback to the devs.
I guess unstable would really be the sunrise overlay. It'd be nice if there were a bit more control over how stuff gets pulled in, eg if we could say "pull in foo and its deps from sunrise and main only" without all the other stuff being considered.