>> The package in question is hard masked ~amd64 > > It's not hard masked. It's only keyword masked. ~amd64 simply means it's > currently in testing and not marked stable yet. And actually, only the > 1.9.0_beta68 of doomsday is in testing. 1.9.0_beta67 is not even keyword > masked. > > Furthermore, your method of installing it: > > ACCEPT_KEYWORDS="~amd64" emerge doomsday > > is wrong. This is only for testing whether it emerges OK and it will be > unmerged again at your next world update. You need to keyword the package > in your package.keywords file/directory.
World updates are rare for me (once every 6 months if that). I come from a slack distro and I'm accustomed to handling everything directly. So I haven't automated system updates in any sort of fashion either. As for this package I am currently in the beta stage you could say, I just want to see it run, then I'll worry about getting runtime configuration that will survive updates. > And no, you can't compile in 32bit mode even if you were using a multilib > profile. Gentoo's multilib is not "real" multilib and won't let you build > in 32bit mode. Bah. That both sucks and blows. Hopefully I can compile beta67 amd64 and get it to run in console mode ( I just want to run a dedicated server for fun ). Alternately I can throw gentoo onto another box/vbox as a 32bit install in order to built this package and run it on amd64 box which is always up.
