Date: Mon, 8 Sep 2014 15:31:14 -0700 From: Patrick <gibblertron@gmail.com> To: Steve Wills <swills@freebsd.org> Cc: freebsd-ruby@freebsd.org Subject: Re: Ruby 2.0 Message-ID: <CA%2BdWbmbsTsBKECbf_6qe-S%2ByO0j=vF%2BeTMWr0M36jwxdfadKbw@mail.gmail.com> In-Reply-To: <20140906193632.GC67217@mouf.net> References: <CA%2BdWbmaPBTMz3MBjq3FjDCaXVOQGKAEM3nkEXKEuXEr7B8Whyg@mail.gmail.com> <20140906193632.GC67217@mouf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 6, 2014 at 12:36 PM, Steve Wills <swills@freebsd.org> wrote: > On Sat, Sep 06, 2014 at 10:04:18AM -0700, Patrick wrote: > > Are there any plans to make Ruby 2.0 (or even 2.1) the default Ruby > version > > for FreeBSD? Most every Ruby developer and company I know has moved past > > 1.9, and the 1.9 default in FreeBSD makes it impossible to use the > official > > pkg sources because any pkg upgrade action wants to replace ruby20 with > > ruby19. While it's probably best that each of us uses our own pkg > > repository built with something like Poudriere, it's definitely not very > > convenient given how much work is involved in setting everything up > that's > > needed to provided a pkg source. > > > > Going from 1.9 to 2.0 is a pretty painless update. > > Yes, it's something that I've been looking at. Exp-run build tests have > been > done several times and I've been using 2.0 as default for packages I build > for > myself for a while, so it's really all ready to go. > > There is one issue, which is the version of devel/ruby-gems. I've been > told by > ruby gems developers that using gem 1.8.x with ruby 2.0 isn't really > supported > or "sane", though I forget the details at this point. So I wanted to get > that > updated before switching the default. Maybe we should just do it without > that, > since I don't know of any specific issues or have details on potential > issues. > > Thoughts? > > Steve > There could be issues working with newer gems: https://github.com/rubygems/rubygems/issues/633 Though it's easy enough to update with `gem update --system`... Would holding it back just be a testing/effort issue, or are there compatibility issues with ruby 1.9? Patrick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BdWbmbsTsBKECbf_6qe-S%2ByO0j=vF%2BeTMWr0M36jwxdfadKbw>