>>> Emerging (20 of 271) app-i18n/prime-1.0.0.1-r2 * prime-1.0.0.1.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * You need to select at least one compatible Ruby installation target via RUBY_TARGETS in make.conf. * Compatible targets for this package are: ruby18 ree18 * * See http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml#doc_chap3 for more information. * * ERROR: app-i18n/prime-1.0.0.1-r2 failed (setup phase): * No compatible Ruby target selected. Most other apps depending on ruby manage to express this through dependencies ...
I'm not really sure if we can handle this situation better, but I'm happy to hear suggestions. I assume your RUBY_TARGETS is set to a non-default "ruby19". We interpret this as that you really don't want "ruby18", so it won't be pulled in as a dependency in any case. Unfortunately prime can only work with ruby18, so now we have an unsolvable situation. We can't express this in normal dependencies because the packages pulling in prime don't and shouldn't know that it is written in ruby.
We'll follow the ruby team's lead on this.
app-i18n/prime is still ruby18-only, so we intend to mask this packages and all packages depending on it. @naota: any change that this can be saved for ruby19 and better? Or can we mask this? Proposed mask would be: app-i18n/prime app-emacs/prime-el app-i18n/gtkimprime app-i18n/scim-prime dev-libs/suikyo and drop "prime" USE flag from app-i18n/uim
Upstream seems to be dead and Debian already dropped the package. Nothing can be done to be saved for ruby19.
@naota: can you proceed with masking the ruby18 only package and its related packages as proposed by graaff?
Masked prime and its related for removal and drop USE=prime from uim.
@ naota: 30 days passed, ready to clean up?
All packages dropped.
