Since ruby bashing is in season, I’ll try to be fashionable. Disclaimer: I don’t use ruby, I have nothing personal against the language, its developers, or Gentoo maintainers. I’m just offering my arch-testing perspective. One job that the x86 arch team has to do is to add the ~x86 keyword to new packages that the maintainers can’t test themselves. The same applies to packages that have new dependencies. Some people (like the ruby team) take this really seriously. Resulting in many keywording bugs for ruby packages and testing those is a real pain. Firstly, circular dependencies: Almost any test of a ruby package depends in a circular way on the package being installed already. The same applies to USE=”doc”. Then the dependencies among the keywording bugs are not properly resolved, that is one needs to figure out which other packages also need keywording, or in which order the bugs are to be processed. All this makes the process require a lot of manual intervention since in automated testing, there are tons of false positives. The amd64 arch does not suffer from this, since the maintainers add their keywords (I think). In the end ruby is an interpreted language. Most packages are arch independent. I suggest the ruby team just add the ~x86 keyword themselves, even if they only tested on ~amd64. Wouldn’t that work?