On 07/09/06, Neil Bothwick <[EMAIL PROTECTED]> wrote:
Just to clarify the point: putting individual packages in package.keywords or package.unmask allows you to use those individual, named, masked packages on a system that wouldn't normally accept them; putting ACCEPT_KEYWORDS="~amd64" makes the system pull in masked packages (rather than unmasked ones) by default.
On Thu, 7 Sep 2006 10:10:01 -0500, John Newman 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~)
It's ~amd64, not amd64~. The way to set this system-wide is to set
ACCEPT_KEYWORDS="~amd64" in /etc/make.conf.
--
Neil Bothwick
I'll be Bach.
-- Johann Sebastian Swartzenegger
Just to clarify the point: putting individual packages in package.keywords or package.unmask allows you to use those individual, named, masked packages on a system that wouldn't normally accept them; putting ACCEPT_KEYWORDS="~amd64" makes the system pull in masked packages (rather than unmasked ones) by default.
Jeff Rollin
--
Proud Linux user since 1998
