Date: Thu, 24 Oct 2013 14:01:24 +0000 From: Steve Wills <swills@freebsd.org> To: Stanislav Sedov <stas@freebsd.org> Cc: Akinori MUSHA <knu@iDaemons.org>, Thomas Abthorpe <tabthorpe@goodking.org>, Bryan Drewery <bryan@shatow.net>, "ruby@FreeBSD.org" <ruby@freebsd.org> Subject: Re: Time to mark lang/ruby18 DEPRECATED Message-ID: <20131024140122.GC92708@mouf.net> In-Reply-To: <0D08EC8B-8E8D-45A6-A53E-6F8EE17B76AC@FreeBSD.org> References: <20130923173906.GR95595@goodking.org> <20130925144423.GI74496@admin.xzibition.com> <861u3cmdyu.knu@iDaemons.org> <0D08EC8B-8E8D-45A6-A53E-6F8EE17B76AC@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 23, 2013 at 11:23:27AM -0700, Stanislav Sedov wrote: > > > At the time we switched to ruby 1.9 there were some ports broken with 2.0 > iirc. I'm not sure if the situation changed with the recent wave of 1.8 ports > deprecation, though. > > I agree that we should go with 2.0. Given that new os x ships with 2.0 we > definitely want to stay compatible with what people are going to use on > OS X. The only major breakages I seen were related to encoding problems > (ruby 2.0 uses utf-8 by default). Unfortunately, some of those problems > only happen at runtime :-( > > Do we have a list of ports broken with 2.0 somewhere? I can't say for runtime issues, but we at least need to have an exp-run. I agree we need to make 2.0 the default, but I'm not sure there is time to do it for 10.0 or that it makes sense given the uncertainty. I'll work on the patch and create the PR to get the exp-run started. Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131024140122.GC92708>