From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Marius Bakke <mbakke@fastmail.com>, guix-devel@gnu.org
Subject: Re: Ruby 2.4.0 update
Date: Mon, 26 Dec 2016 23:18:52 +1000 [thread overview]
Message-ID: <7d94e235-d02c-38f2-7c72-358b2fd123be@uq.edu.au> (raw)
In-Reply-To: <878tr4ndeq.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
Thanks Marius, an enjoyable xmas read of all the new features it was.
On 26/12/16 03:09, Marius Bakke wrote:
> In good tradition, ruby made a new release today (25/12)[0].
>
> I tried building some packages with the new version, but ruby-minitest
> complains that Rake 12 is too new (even with the latest minitest). There
> have been some core changes as well, with Fixnum and Bignum now merged
> into a single Integer class.
I updated ruby-minitest to the newest version and pushed, but as you
mention the check phase requires rake <12. This actually stems from hoe
though rather than minitest, I've asked the devs about it here:
https://github.com/seattlerb/hoe/issues/77
I'm not sure that the Fixnum/Bignum changes are particularly harmful if
I'm understanding correctly, since both classes can still be used. I
can't see any possible backwards incompatibility.
> I suggest that we keep ruby 2.3 as the main "ruby" variable until the
> ecosystem catches up. Users will still get the latest version when
> using `guix package` or `guix environment`. WDYT?
I would agree, but I'd hope that the hoe issue is an isolated one and
that we can make ruby-2.4 the default very soon.
When we do such an update, I think we should make ruby inherit from
ruby-2.3 as discussed previously. Also, what would you say to setting
the "--jemalloc" configure flag for speed and compiling with gcc-5, both
for speed?
Thanks, ben.
next prev parent reply other threads:[~2016-12-26 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 17:09 Ruby 2.4.0 update Marius Bakke
2016-12-26 13:18 ` Ben Woodcroft [this message]
2017-01-05 11:16 ` Ben Woodcroft
2017-01-05 13:20 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d94e235-d02c-38f2-7c72-358b2fd123be@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).