When you add a line to the package.keywords file, but leave-out any actual keywords for a specified package, it automatically implies that you want to accept the unstable keyword for your particular architecture. However, eix doesn't seem to honor this implication. Say, for example, you want the latest version of Vim, even if it's unstable for your architecture. You would simply add this line to your package.keywords file: app-editors/vim You could then run the following command to check if Vim is now upgradeable: eix --versionlines --upgrade vim No results would be returned. But if you went back and added "~amd64" (or "~x86", etc.) to the end of the line in package.keywords, only then would it show you that vim is upgradeable -- while Portage would still allow you to upgrade Vim with the line formatted either way.
What you want is implemented in eix since many versions: An empty line in /etc/portage/package.keywords is like adding ~ARCH for all values in your ARCH variable. Are you sure that your ARCH variable is set correctly (e.g. by chosing the profile) and not overridden e.g. by your environment? Which version of eix are you using?
(In reply to comment #1) > What you want is implemented in eix since many versions: closing then.