Martin, Gentoo Prefix users need to set "ALWAYS_ACCEPT_KEYWORDS="true"" in ~/.eixrc to get sane output. Perhaps it is easier to show you. without: %% eix -e less [I] sys-apps/less Available versions: (~*)436{tbz2} (~*)440 {unicode} Installed versions: 440(03:47:38 PM 02/01/2011)(unicode) Homepage: http://www.greenwoodsoftware.com/less/ Description: Excellent text file viewer with: %% eix -e less [I] sys-apps/less Available versions: 436{tbz2} 440 {unicode} Installed versions: 440(03:47:38 PM 02/01/2011)(unicode) Homepage: http://www.greenwoodsoftware.com/less/ Description: Excellent text file viewer Is there any way we could get something that works out of the box here?
I am not sure what want me to do: Doing some runtime magic depending on ARCH (e.g. forcing ALWAYS_ACCET_KEYWORDS=true if ARCH contains certain values) might be a bit confusing. I could add a ./configure switch to set the default of ALWAYS_ACCEPT_KEYWORDS; this switch could then be set by the ebuild depending on ARCH.
Yea, I figured you were looking at the $ARCH value. That only confuses eix on the profiles where Gentoo Prefix doesn't match $ARCH to $ACCEPT_KEYWORDS, so x86-linux, amd64-linux, *-freebsd iirc.
(In reply to comment #2) > where Gentoo Prefix doesn't match $ARCH to $ACCEPT_KEYWORDS, so > x86-linux, amd64-linux, *-freebsd iirc. Maybe I do not understand something: Do you mean you have ARCH="x86-linux" in the profile but only ACCEPT_KEYWORDS="~x86" (and not ACCEPT_KEYWORDS="~x86-linux") in your make.conf? If this is the case, how does portage know that "-linux" must be appended?
(In reply to comment #3) > Maybe I do not understand something: > Do you mean you have ARCH="x86-linux" in the profile but only > ACCEPT_KEYWORDS="~x86" (and not ACCEPT_KEYWORDS="~x86-linux") > in your make.conf? > If this is the case, how does portage know that "-linux" must be appended? > Incorrect. example: ARCH=x86 & ACCEPT_KEYWORDS=~x86-linux You can see for yourself in $PORTDIR/profiles/prefix, example: /usr/portage/profiles/prefix/linux/x86/make.defaults
Alternatively, we can just add "use prefix && echo 'ALWAYS_ACCET_KEYWORDS=true' >> $ED/etc/eixrc" or so. That may be easier.
In eix trunk, I have now introduced the value "full" for ACCEPT_KEYWORDS_AS_ARCH (and this is now the default value of that variable). This causes that ARCH is replaced by the modification of ACCEPT_KEYWORDS, but only with the stable versions. For instance, in your example you should now get something like %% eix -e less [I] sys-apps/less Available versions: (~)436 (~)440 {unicode} ... which is perhaps the most "logical" result, although perhaps still not acceptable for arches which will never go stable. In any case, I have also introduced ./configure --with-always-accept-keywords to set the default of ALWAYS_ACCEPT_KEYWORDS, so that you can use econf ... $(use_with prefix always-accept-keywords) ... in the ebuild.
I'll see how this looks next week. Thanks.
(In reply to comment #7) > I'll see how this looks next week. Thanks. Added, $(use_with prefix always-accept-keywords) to 0.22.8
