646528 – dev-lang/ruby: probable RUBY_TARGETS USE flags issue

Bug 646528 - dev-lang/ruby: probable RUBY_TARGETS USE flags issue

Summary: dev-lang/ruby: probable RUBY_TARGETS USE flags issue

Status:	RESOLVED CANTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Ruby Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2018-02-03 22:19 UTC by Viktor Levin
Modified:	2018-07-20 19:09 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
RUBY_TARGETS USE flags warning (ruby_targets_warning.txt,2.58 KB, text/plain) 2018-02-03 22:19 UTC, Viktor Levin	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Viktor Levin 2018-02-03 22:19:50 UTC

Created attachment 517704 [details]
RUBY_TARGETS USE flags warning

In /etc/portage/make.conf, I have:

ACCEPT_KEYWORDS="* ~*"
EMERGE_DEFAULT_OPTS="--ask --ask-enter-invalid --backtrack=9999 --changed-deps-report --complete-graph --deep --jobs=12 --tree --verbose --verbose-conflicts --with-bdeps=y"

When I execute "emerge -uN @world", I see this USE flags processing warning:
(see ruby_targets_warning.txt attachment)

By the way, I do not set RUBY_TARGETS option in make.conf (it is default).

But when I add
>=dev-lang/ruby-2.4::gentoo
to /etc/portage/package.mask/ruby.mask, I see no RUBY_TARGETS USE flags warnings (it works properly and does not try to emerge dev-lang/ruby:2.5).

Is it a bug of Ruby-related eclasses?

Comment 1 Jeroen Roovers (RETIRED) gentoo-dev

2018-02-05 16:58:24 UTC

Don't do that.

Comment 2 Viktor Levin 2018-02-05 18:46:00 UTC

(In reply to Jeroen Roovers from comment #1)
> Don't do that.
Okay.

Comment 3 Hans de Graaff gentoo-dev

2018-07-20 19:09:36 UTC

This can't be helped because we can only provide a single RUBY_TARGETS default for both stable and testing. We've opted to make this default match stable so that things for stable users work out of the box. If you are on testing you should either include the new ruby versions in RUBY_TARGETS yourself or mask the new versions until they are stable.