From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ruby - 3 versions - seriously????
Date: Mon, 4 Sep 2017 13:49:05 -0400 [thread overview]
Message-ID: <9c252058-69fb-e504-1ca0-a7381f9ceaee@gentoo.org> (raw)
In-Reply-To: <CAAD4mYjsGidrayyt32uZZ6HvZJ51SpjoCYspsNKzFwjcqi-j6Q@mail.gmail.com>
On 09/04/2017 01:07 PM, R0b0t1 wrote:
>
> For almost all languages but Ruby (and Perl) you can take code written
> against one minor version and compile it in the next minor version.
This isn't a language issue with Ruby, it's a culture/package-management
one. For a long time, it's been easy to bundle dependencies in Ruby. The
result is a culture of saying "I need the version of ruby-foo that was
released on my birthday that one time mercury was in retrograde, and
also I'd like the version number to have a seven in it somewhere because
that's my daughter's age." When two package authors come up with two
different requirements like that, you end up needing *two* versions of
ruby-foo installed.
Even if both packages could happily use the same, latest version of
ruby-foo -- you get what upstream says in most cases. And what upstream
says is usually crap, because they bundle everything and will never
notice annoying incompatibilities like end-users do.
next prev parent reply other threads:[~2017-09-04 17:49 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 [this message]
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 ` [gentoo-user] " Hans de Graaff
2017-09-03 5:54 ` 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=9c252058-69fb-e504-1ca0-a7381f9ceaee@gentoo.org \
--to=mjo@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