| 1 |
On Thu, Dec 04, 2008 at 12:58:28AM +0530, Penguin Lover Rajat Vig squawked: |
| 2 |
> The 9999 Builds are Live CVS Builds. |
| 3 |
> The default is to use the Snapshot builds which are getting pulled in. |
| 4 |
> |
| 5 |
> -Rajat |
| 6 |
> |
| 7 |
|
| 8 |
Okay, a better question then is: how does |
| 9 |
|
| 10 |
> > case ${EKEY_STATE:-${E_STATE}} in |
| 11 |
> > release) KEYWORDS="alpha amd64 arm hppa ia64 mips ppc ppc64 sh sparc |
| 12 |
> > x86 ~x86-fbsd";; |
| 13 |
> > snap) KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 |
| 14 |
> > ~sh ~sparc ~x86 ~x86-fbsd";; |
| 15 |
> > live) KEYWORDS="";; |
| 16 |
> > esac |
| 17 |
|
| 18 |
know that the 9999 ebuilds should be live, and that default it should |
| 19 |
be snap? I am completely puzzled by the ebuilds. |
| 20 |
|
| 21 |
In other words, is it hardcoded somethere in portage that all 9999 |
| 22 |
version numbers automatically trigger that variable above to be live? |
| 23 |
Or is there some configuration somewhere? |
| 24 |
|
| 25 |
Also, is this what all that fuss about EAPI is about? The |
| 26 |
enlightenment ebuilds in the tree looks quite different from the ones |
| 27 |
in the overlay. |
| 28 |
|
| 29 |
Thanks, |
| 30 |
|
| 31 |
W |
| 32 |
-- |
| 33 |
ZM: prolly |
| 34 |
ZM: eeb's are weird |
| 35 |
Sortir en Pantoufles: up 726 days, 23:12 |
Archives