On Thursday 12 April 2007 15:02:28 Alan McKinnon wrote: > There are not one but TWO ways that packages get masked.
Actually there's at least 3 possible masking reasons.. ~arch keyword, missing keyword and package.mask. Also the missing keyword reason is overloaded. [SNIP] > [...] and 'ACCEPT_KEYWORDS=~x86' if you want unstable/testing. I don't think anyone should ever mention ACCEPT_KEYWORDS=~arch without making it clear that going back from all ~arch to stable is very hard and in certain special cases dangerous (mostly glibc downgrades). > So much for stable/testing. There's another way to use all this, that is > packages that don;t have any keywords at all. These are new ebuilds put > in portage for the first stage of testing. [SNIP] > Now, eclipse-core is in this category: Umm... no it isn't. It's ~x86 and package.mask'ed. Other ebuilds belonging to that category are socalled live ebuilds that pull latest version of a package from the version control system that upstream is using. A test of those today may not be valid tomorrow and hence they can't be keyworded. Useful for developers only. > nazgul enlightenment # eix eclipse-core > * dev-java/eclipse-core > Available versions: (3) [M](~)3.2_pre2 [SNIP] > See the [M] on the versions line? That says it's hard masked and you > need to do this to get it going: > > echo "dev-java/eclipse-core -*" >> /etc/portage/package.keywords Wrong! > Note the -* in the echo command, it is needed. It tells emerge to > install that package regardless of the fact that it has no keywords set > in the ebuild. No it doesn't. It tells emerge to install packages that have -* in KEYWORDS. For no keywords at all you need **. In this case you just need ~x86 and package.unmask.. -- Bo Andresen
pgplKqDuZ1RSw.pgp
Description: PGP signature
