portageq in 2.0.51 is not behaving as expected which breaks crossdev and possibly other scripts. (02:59:31 Fri Jun 18 2004 root@cid x86_64) /usr/tmp/portage $ export ACCEPT_KEYWORDS="-* sparc" (02:59:39 Fri Jun 18 2004 root@cid x86_64) /usr/tmp/portage $ /usr/bin/portageq best_visible / sys-devel/binutils (02:59:42 Fri Jun 18 2004 root@cid x86_64) /usr/tmp/portage $ qpkg -I -v portage sys-apps/portage-2.0.51_pre10 * app-portage/ufed-0.34 * app-portage/gentoolkit-dev-0.2.0_pre3 * app-portage/gentoolkit-0.2.0_pre8 * --- (09:59:07 Fri Jun 18 2004 jeremy@cid i686) ~ $ export ACCEPT_KEYWORDS="-* sparc" (10:00:13 Fri Jun 18 2004 jeremy@cid i686) ~ $ /usr/bin/portageq best_visible / sys-devel/binutils sys-devel/binutils-2.14.90.0.7-r4 (10:00:17 Fri Jun 18 2004 jeremy@cid i686) ~ $ qpkg -I -v portage sys-apps/portage-2.0.50-r8 * app-portage/ufed-0.34 * app-portage/gentoolkit-dev-0.2.0_pre1 * app-portage/gentoolkit-0.2.0_pre8 *
The KEYWORDS that are accepted are a combination of ACCEPT_KEYWORDS as well as your /etc/make.profile/make.defaults:ARCH. I'm not sure how this crossdev script works, but portage does not yet support cross-compiling. When it does, it is likely that ${ROOT}/etc/make.profile will be used instead.
is tehre a way to override the settings in the profile with envvars? I tried 'export ARCH=sparc' and that failed to give the expected response to portageq.
I believe Jeremy and Brian are working toward getting cross-compiling support working for the 2.1.X tree, with config and build profiles.
Closing due to old age.