Bug 911714 – make.defaults: Add USE_EXPAND="RUBY_SINGLE_TARGET"

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description konsolebox 2023-08-04 16:52:31 UTC]

Please add USE_EXPAND="RUBY_SINGLE_TARGET" to base/make.defaults so USE="ruby_single_target_ruby32" can be specified using RUBY_SINGLE_TARGET="ruby32" instead.  I just made an update implementation of my Ruby script package that only works against one Ruby implementation at a time with shebang header as #!/usr/bin/rubyXX so any form of `eselect ruby` won't affect its runtime.

If possible also kindly add desc/ruby_single_target.desc, probably with the following content based on desc/python_single_target.desc:

--------------------
# Copyright 1999-2023 Gentoo Authors.
# Distributed under the terms of the GNU General Public License v2

# This file contains descriptions of RUBY_SINGLE_TARGET USE_EXPAND flags.

ruby30 - Build for Ruby 3.0 only
ruby31 - Build for Ruby 3.1 only
ruby32 - Build for Ruby 3.2 only
--------------------

[Comment 1 Sam James 2023-08-04 16:57:14 UTC]

Such changes should be done via the mailing list (use `git-send-email`).

But really this needs eclasses to go with it, not just adding the USE_EXPAND by itself, which will end up confusing people. (This _does_ need doing, it's just that the USE_EXPAND is really the trivial part.)

[Comment 2 konsolebox 2023-08-04 17:26:11 UTC]

Alright I'll just consider this as unapproved until devs implement it.  The eclass in my opinion is for the devs.  The users will understand it if there's the desc.

[Comment 3 Sam James 2023-08-04 17:28:18 UTC]

(In reply to konsolebox from comment #2)
> Alright I'll just consider this as unapproved until devs implement it.  The
> eclass in my opinion is for the devs.  The users will understand it if
> there's the desc.

I mean, anyone is free to implement it, including you.

I don't get what "unapproved" means. I just mean there's no point in committing the RUBY_SINGLE_TARGET USE_EXPAND by itself without eclass work.