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