1. Different versions of Python.
# echo 'USE_PYTHON="2.4 2.5 2.6 2.7"' >> /etc/make.conf
# emerge python:2.{4..7}
Doing so once should cause bzr to be installed and tested for all four versions of python, using the commands above.
2. Stable and testing.
It would be nice to have two setups of Gentoo, one at stable (e.g. ACCEPT_KEYWORDS=amd64 in /etc/make.conf) and the other at testing (e.g. ACCEPT_KEYWORDS=~amd64). This would influence the version numbers of a large number of direct and indirect dependencies, and should reflect common sets of package versions installed by Gentoo users.
Thanks for making this effort of getting the selftests running on Gentoo! I guess that there still will be a large number of possible combinations of configuration details out in the wild, way too many to test up front. So there may still be occasional bug reports coming in from users, in which case we'd have to identify the involved config aspects and perhaps add them to the testing server in one way or another. Think of it as a community testing effort...
Thinking about other permutations worth trying:
1. Different versions of Python.
# echo 'USE_PYTHON="2.4 2.5 2.6 2.7"' >> /etc/make.conf
# emerge python:2.{4..7}
Doing so once should cause bzr to be installed and tested for all four versions of python, using the commands above.
2. Stable and testing. KEYWORDS= amd64 in /etc/make.conf) and the other at testing (e.g. ACCEPT_ KEYWORDS= ~amd64) . This would influence the version numbers of a large number of direct and indirect dependencies, and should reflect common sets of package versions installed by Gentoo users.
It would be nice to have two setups of Gentoo, one at stable (e.g. ACCEPT_
Thanks for making this effort of getting the selftests running on Gentoo! I guess that there still will be a large number of possible combinations of configuration details out in the wild, way too many to test up front. So there may still be occasional bug reports coming in from users, in which case we'd have to identify the involved config aspects and perhaps add them to the testing server in one way or another. Think of it as a community testing effort...