From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] (masked by: missing keyword)
Date: Sat, 29 Oct 2005 15:18:32 +0200 [thread overview]
Message-ID: <436376A8.5040705@planet.nl> (raw)
In-Reply-To: <43636843.3040704@comcast.net>
sean schreef:
> What is the proper way to over ride a package that is (masked by:
> missing keyword)? From what I read it is supposed to be done with the
> package.keywords file in /etc/portage. But I must be doing something
> wrong with format.
>
> Specifically I am trying to install openoffice 2.0 on my amd64
> system. I have unmasked it, but the keyword is still blocking me.
>
> Thanks Sean
'Missing keyword' is a very specific state, different from masking,
keyword ~arch, or other kinds of blocks;
>From packages.gentoo.org
openoffice
Description: OpenOffice.org, a full office productivity suite.
Releases alpha amd64 arm hppa ia64 mips ppc ppc64 ppc macos s390 sparc x86
2.0.0 - - - - - - ~ - -
- - ~
You see that "-" under the alpha, amd64, arm, hppa and all other
architectures than ppc and x86?
Those "-" are missing keywords. This package is only rated (as unstable)
for ppc and x86 architectures. On all other arches, the build is so
unstable, or so untested, that it is not keyworded at all.
Which is why the legend on p.g.o says
"- not available"
Now, if you really really want to test such a build in the name of
science, you can of course do so, but you will have to jump through a
hoop or two because you really are not meant to be using this package
unless you mean to help troubleshoot:
First thing to do is to add to /etc/portage/package.keywords:
app-office/openoffice -*
This will unmask the build with the missing keyword.
Try running the emerge again, but there's a fair likelihood that you
will hit a further mask, like package.mask.
If so, you should again consider if you *really* want to unmerge this
package; if it's masked up the wazoo, are you sure that you have the
time and energy to deal with the problems it apparently has, and help
solve them? If not, find an alternative (like openoffice-bin, which is
marked as unstable for amd64).
If so, then add the package to /etc/portage/package.unmask
=app-office/openoffice-2.0.0
and see how far you get.
Be warned, it's quite possible that the package will not compile, or
will have problems compiling-- openoffice is quite hard to compile under
the best of circumstances, and these are not them. There have been a lot
of changes, both in the program itself (hence the 2.0 version) and in
the supporting infrastructure (gtk libraries, freedesktop.org specs, X
itself not to mention the deeper backend libraries), and how these
things are going to interact on a 'sensitive' system architecture is
anybody's guess.
But of course, somebody has to take the plunge and report back for the
issue to progress any further, so if you want to do that, good luck.
If you don't want to do that, but rather just use the program, unmask
and install the bin package.
HTH,
Holly
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-29 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 12:17 [gentoo-user] (masked by: missing keyword) sean
2005-10-29 12:33 ` Dale
2005-10-29 16:14 ` sean
2005-10-29 13:18 ` Holly Bostick [this message]
2005-10-29 16:14 ` sean
2005-10-29 16:32 ` Holly Bostick
2005-10-29 20:40 ` Ciaran McCreesh
2005-10-31 1:00 ` [gentoo-user] " Tim Kruse
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=436376A8.5040705@planet.nl \
--to=motub@planet.nl \
--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