On Saturday 25 March 2006 18:54, JimD <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-user] net-misc/rinetd': > On Sat, 25 Mar 2006 17:49:53 -0600 > > "Boyd Stephen Smith Jr." <[EMAIL PROTECTED]> wrote: > > 2 options: > > 1) Add a /valid/ keyword to your package.keywords like '~x86' or > > 'x86'. 2) Use a portage overlay. > > Why isn't ~* valid?
From man 5 ebuild:
---
KEYWORDS = [-~][x86,ppc,sparc,mips,alpha,arm,hppa]
Should contain appropriate list of arches that the ebuild is
know to work/not work. By default if you do not know if an ebuild runs
under a
particular arch simply omit that KEYWORD. If the ebuild
will not work on that arch include it as -ppc for example. If the ebuild
is being
submitted for inclusion, it must have ~arch set for
architectures where it has been PROVEN TO WORK. (Packages KEYWORDed
this way may be
unmasked for testing by setting ACCEPT_KEYWORDS="~arch"
on the command line, or in make.conf(5)) For an authoritative list please
review
/usr/portage/profiles/arch.list. Please keep this list in
alphabetical order.
---
(Sorry that didn't wrap right.)
There's also a special -*, but I'm not sure /exactly/ how that works.
I knew to look in man 5 ebuild because of this snippet from man portage:
---
KEYWORD
Each architecture has a unique KEYWORD.
More reading: ebuild(5)
---
I don't know where your ~* came from. Heck, maybe that /is/ valid and
something is really wrong with your portage. Can anyone else throw in on
this issue? A dev, maybe?
--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
pgpcLIILdScLM.pgp
Description: PGP signature
