public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Missing Keyword
Date: Thu, 23 Feb 2006 15:32:01 -0600	[thread overview]
Message-ID: <200602231532.01499.bss03@volumehost.com> (raw)
In-Reply-To: <bba6100b0602231238m1454f3deye7773bdce15e22c3@mail.gmail.com>

On Thursday 23 February 2006 14:38, "Nick Smith" <nick.smith79@gmail.com> 
wrote about 'Re: [gentoo-user] Missing Keyword':
> > Use /etc/portage/package.keywords (with an actual keyword, instead of
> > the default ~ARCH) or your local overlay.
>
> what is the actual keyword if it doesnt have one? just add it to my
> package.keywords file and add the arch to it? i dont see how that
> would work.

Sorry, my explanation was a bit terse.

Masked due to "missing keyword" means that none of the keywords in 
ACCEPT_KEYWORDS match with any of the keywords in the ebuilds KEYWORDS.

So, an ebuild that has KEYWORDS="x86 ~hppa ~sparc" will match any x86 
profile but only testing hppa or sparc machines.  Attempt to install it on 
an amd64 machine results in a "missing keyword".  You would have to view 
the individual ebuild to determine what KEYWORDS it has.

/etc/portage/package.keywords is a way to add to ACCEPT_KEYWORDS on a 
per-package basis.  /Most of the time/, it is used to install testing 
versions; if you don't supply a keyword after the package atom portage 
assumes you meant ~${ARCH}.  However, it can be used to accept other 
keywords, you just have to put them there.  amd64 users will probably find 
this most useful since it is more likely that something that works on x86 
also works on amd64 than it is that something that works on hppa works on 
sparc -- that is there are keywords other than ~${ARCH} that may be of 
real use.

For the crazier amd64 users out there, yes this does mean you could have 
ACCEPT_KEYWORDS="~amd64 x86" or even "~amd64 x86 ~x86" in your make.conf, 
but I don't recommend it.  (The transition from 32-bit to 64-bit is not 
easy for all programs.)

Also, I seem to remember that package.keywords didn't always default to 
~${ARCH}.  Am I mis-remembering that?  Do any developers here know for 
sure?

-- 
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2006-02-23 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 18:07 [gentoo-user] Missing Keyword Nick Smith
2006-02-23 20:23 ` Boyd Stephen Smith Jr.
2006-02-23 20:38   ` Nick Smith
2006-02-23 21:07     ` Uwe Thiem
2006-02-23 21:32     ` Boyd Stephen Smith Jr. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200602231532.01499.bss03@volumehost.com \
    --to=bss03@volumehost.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox