On 07/09/06, A. R. <[EMAIL PROTECTED]> wrote:
> Up until now, to remedy this when I want to attempt to use one of these
> packages, I simply edit the ebuild, regenerate the digest, and do the
> installation. I feel sure there is an easier way around this - I've
> read somewhere of being able to tell the system that I am not worried
> about packages that haven't been tested on amd64 (thus the amd64~) -
> does anyone know what file I need to edit and in what way to make this
> work so I don't have to go through the hassle described above of editing
> the ebuild, regenerating the digest and then installing the package?
Sure there is:
/etc/portage/package.keywords
where each line is the full package name that you want to allow
"~amd64" for your system. (in your case)
An example is:
x11-themes/gtk-engines-qt
Save it and then just run:
emerge -vuD world -p
and you'll se portage telling you that is going to bring in the latest
"keyworded" version of such package.
HTH
- AR
--
If you stare long enough into an abyss, the abyss will stare back into you...
--
[email protected] mailing list
As an aside:
1. Some ebuilds are "masked packages". Whilst the chances of them being functional are *considerably smaller* than if they are marked ~amd64, if you REALLY must use them you can do so by putting their names into "/etc/portage/package.unmask" in a similar format to the above.
2. Whilst I appreciate the courtesy (!), posts are more likely to stand out, and therefore be read, if they have a more "on-topic" subject line than "hello", or some such. For example, a better one for this thread might be "how to unmask packages?" or even just "amd64?".
In addition, some anti-spam software *might* throw away messages like ones which have a subject line "hello," when they otherwise might catch the attention of someone able and willing to help you.
HTH.
Jeff Rollin
--
Proud Linux user since 1998
