You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by sebb <se...@gmail.com> on 2016/03/20 10:14:06 UTC

Update Whimsy to use Ruby 2.3.0 throughout?

At present Passenger uses 2.3.0, but most of the other scripts use the
default Ruby which is 1.9.3.

The Ruby 2.x versions have many improvements and new features (e.g.
__dir__ and to_h).

It's likely that developers will be using a later version than 1.9.3.
This makes it harder to test whether the code is compatible with that
version without deploying it and seeing if it breaks...

The simplest solution might be to link /usr/local/bin/ruby to ruby2.3.0.
It looks like /usr/local/bin is on the PATH ahead of /usr/bin so that
should just work.

Might it be worth trying that?

Re: Update Whimsy to use Ruby 2.3.0 throughout?

Posted by sebb <se...@gmail.com>.
Created branch: sebb-20160321 which I hope is OK

On 20 March 2016 at 12:32, Sam Ruby <ru...@intertwingly.net> wrote:
> +1
>
> - Sam Ruby
>
> On Sun, Mar 20, 2016 at 5:14 AM, sebb <se...@gmail.com> wrote:
>> At present Passenger uses 2.3.0, but most of the other scripts use the
>> default Ruby which is 1.9.3.
>>
>> The Ruby 2.x versions have many improvements and new features (e.g.
>> __dir__ and to_h).
>>
>> It's likely that developers will be using a later version than 1.9.3.
>> This makes it harder to test whether the code is compatible with that
>> version without deploying it and seeing if it breaks...
>>
>> The simplest solution might be to link /usr/local/bin/ruby to ruby2.3.0.
>> It looks like /usr/local/bin is on the PATH ahead of /usr/bin so that
>> should just work.
>>
>> Might it be worth trying that?

Re: Update Whimsy to use Ruby 2.3.0 throughout?

Posted by Sam Ruby <ru...@intertwingly.net>.
+1

- Sam Ruby

On Sun, Mar 20, 2016 at 5:14 AM, sebb <se...@gmail.com> wrote:
> At present Passenger uses 2.3.0, but most of the other scripts use the
> default Ruby which is 1.9.3.
>
> The Ruby 2.x versions have many improvements and new features (e.g.
> __dir__ and to_h).
>
> It's likely that developers will be using a later version than 1.9.3.
> This makes it harder to test whether the code is compatible with that
> version without deploying it and seeing if it breaks...
>
> The simplest solution might be to link /usr/local/bin/ruby to ruby2.3.0.
> It looks like /usr/local/bin is on the PATH ahead of /usr/bin so that
> should just work.
>
> Might it be worth trying that?