From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: dhk <dhkuhl@optonline.net>
Subject: Re: [gentoo-user] Keyword for dev-java/sun-j2ee
Date: Thu, 11 Feb 2010 17:25:57 +0200 [thread overview]
Message-ID: <201002111725.58084.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4B741AB3.8010802@optonline.net>
On Thursday 11 February 2010 16:56:51 dhk wrote:
> Alan McKinnon wrote:
> > On Thursday 11 February 2010 15:19:57 dhk wrote:
> >> How do I find out the missing keyword for dev-java/sun-j2ee?
> >>
> >> I tried dev-java/sun-j2ee ~amd64 java in /etc/portage/package.keywords
> >> and tried adding ACCEPT_LICENSE="sun-bcla-j2ee" to /etc/make.conf.
> >
> > dev-java/sun-j2ee ~*
> >
> >> Below is the output to the emerge.
> >>
> >> emerge -pv dev-java/sun-j2ee
> >> !!! CONFIG_PROTECT is empty
> >> These are the packages that would be merged, in order:
> >>
> >> Calculating dependencies... done!
> >>
> >> !!! All ebuilds that could satisfy "dev-java/sun-j2ee" have been masked.
> >> !!! One of the following masked packages is required to complete your
> >> request:
> >> - dev-java/sun-j2ee-1.3.1-r4 (masked by: missing keyword)
> >>
> >>
> >> For more information, see the MASKED PACKAGES section in the emerge
> >> man page or refer to the Gentoo Handbook.
> >>
> >> Thanks,
> >>
> >> dhk
>
> That seems like it should have worked. I tried dev-java/sun-j2ee ~* in
> /etc/portage/package.keywords but I get the same response.
>
> Any more ideas?
From the ebuild:
KEYWORDS="-ppc x86"
So for amd64 you would need in packages.keywords:
dev-java/sun-j2ee **
That will likely let it install. It might even run afterwards... :-)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2010-02-11 15:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 13:19 [gentoo-user] Keyword for dev-java/sun-j2ee dhk
2010-02-11 14:40 ` Alan McKinnon
2010-02-11 14:56 ` dhk
2010-02-11 15:25 ` Alan McKinnon [this message]
2010-02-11 15:46 ` Dale
2010-02-11 16:09 ` Alex Schuster
2010-02-11 18:28 ` Alan McKinnon
2010-02-11 19:49 ` Neil Bothwick
2010-02-11 23:51 ` Dale
2010-02-12 6:25 ` Alan McKinnon
2010-02-12 11:13 ` Dale
2010-02-11 16:36 ` dhk
2010-02-11 20:06 ` dhk
2010-02-11 20:31 ` Alan McKinnon
2010-02-11 22:10 ` dhk
2010-02-11 22:20 ` Alan McKinnon
2010-02-11 22:58 ` dhk
2010-02-11 23:12 ` Alan McKinnon
2010-02-11 23:28 ` dhk
2010-02-14 20:37 ` dhk
2010-02-15 7:16 ` Alan McKinnon
2010-02-11 21:06 ` [gentoo-user] " walt
2010-02-11 22:11 ` dhk
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=201002111725.58084.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=dhkuhl@optonline.net \
--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