Thanks for the response.
On 2022.10.11 16:07, Arve Barsnes wrote:
On Tue, 11 Oct 2022 at 22:02, Jack <ostrof...@users.sourceforge.net>
wrote:
> Does anybody see what I'm missing?
Maybe you have something in package.use for this package?
"grep -ir thor ." in /etc/portage has no hits. In addition "grep -ir
ruby ." in /etc/portage shows only package.accept_keyword entries and
RUBY_TARGETS="ruby31" in make.conf.
You could try to get emerge to tell you more explicitly what problem
it has
USE="ruby_targets_ruby31" emerge -av dev-ruby/thor
I don't see how this is any different from putting it in package.use,
but it has the same lack of effect.
Regards,
Arve
Can anyone explain (or point me the the fine manual page I missed) the
exact meaning of (-ruby31) in
!!! The ebuild selected to satisfy "dev-ruby/thor" has unmet
requirements.
- dev-ruby/thor-1.2.1::gentoo USE="-doc -test" ABI_X86="(64)"
RUBY_TARGETS="-ruby27 (-ruby30) (-ruby31)"
and why is ruby27 not in parens, but the other two are? Is that just
the assumption that ruby31 is off in any ebuild which does not
explicitly mention it, or does it reflect an explicit turning off of
that flag?
Jack
