public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Ruby - 3 versions - seriously????
Date: Sun, 3 Sep 2017 08:08:43 +0200	[thread overview]
Message-ID: <bsis7e-bqg.ln1@graaff.xs4all.nl> (raw)
In-Reply-To: 9dfc7db0-cf95-e420-5f1d-c664ab547f2f@gmail.com

On Sat, 02 Sep 2017 22:57:12 +0200, Alan McKinnon wrote:

> OK, so disclaimer up front. I detest Ruby. I hate it with a passion.

Personally I find that passion is better reserved for positive things.

> You have to understand what Ruby is. It is not a language. It is 5
> languages. Like python27 and python3 are really different languages with
> much in common. The difference is the python devs have solid reasons for
> doing python3 and the transition has been mostly smooth. Each new minor
> version of ruby is a whole new language and the devs are OK with large
> breaking changes between minor version numbers.

I'm not sure this is fully fair to both ruby and python. Yes, there are 
incompatibilities between ruby versions, sometimes even large ones (1.8 
to 1.9 certainly had them), but recent versions haven't seen major 
changes and for the most part all ruby code in the gentoo repository 
works with all versions. To say that the python3 transition has been 
smooth probably doesn't do justice to the slow uptake.

> So why 3 rubys? Because they are 3 languages and you have packages that
> for whatever reason are tied to different rubys. Just pretend to
> yourself that they aren't really ruby22, ruby23 and ruby24 - they are
> php, perl and python (or whatever 3 language names you like that help
> you get past the 3 rubys! thing).

The situation with ruby really isn't different from python or perl at 
all. We also have multiple python versions in the tree just like with 
ruby. perl is not slotted but faces the same issues on each version (e.g. 
the "no . in INC path anymore" issue that made ruby 1.8 to 1.9 such a big 
deal).

> You probably need all 3. As housekeeping, you can put this in make.conf:
> RUBY_TARGETS="ruby22",
> and remove all ruby versions from world and let depclean, revdep-rebuild
> and emerge world take care of the details.

I find it very unlikely that you would *need* all three versions, unless 
you are doing ruby development and want to actively use all three. The 
RUBY_TARGETS="ruby22" advice matches the current default in the profile.

Until recently we had four different ruby versions, so we are already 
improving here. The end goal is to only have the two latest versions in 
the tree.

Hans



  parent reply	other threads:[~2017-09-03  7:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02 13:33 [gentoo-user] Ruby - 3 versions - seriously???? Andrew Lowe
2017-09-02 13:57 ` Peter Humphrey
2017-09-02 20:57 ` Alan McKinnon
2017-09-02 21:37   ` Marvin Gülker
2017-09-03  2:18     ` R0b0t1
2017-09-03 10:31       ` Marvin Gülker
2017-09-03 20:35         ` R0b0t1
2017-09-04  6:49           ` Marvin Gülker
2017-09-04 17:07             ` R0b0t1
2017-09-04 17:49               ` Michael Orlitzky
2017-09-04 21:15                 ` R0b0t1
2017-09-04 20:32               ` Marvin Gülker
2017-09-04 23:40                 ` R0b0t1
2017-09-05 12:46                 ` konsolebox
2017-09-03  6:08   ` Hans de Graaff [this message]
2017-09-03  5:54 ` [gentoo-user] " Hans de Graaff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bsis7e-bqg.ln1@graaff.xs4all.nl \
    --to=graaff@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox