Get the code ready for Ruby 2.0

[GoogleCodeExporter]

I've heard rumours (but haven't seen any error reports yet) that with ruby 2.0, 
GeoToad would fail miserably.

Although Ruby 1.9 supposedly will be supported for a while (1.8 was just phased 
out a few months ago), we should be ready for the transition in the not-so-far 
future.

The major obstacle I'm facing is that, for Debian Wheezy, there's no pre-built 
package of ruby2.0 available. I could make my own, by merging a previous 
debian/ tree with the latest source tarball - true, but also  time-consuming 
(and I'd have to get all the dependencies right...). I'll rather wait for a 
backported package to become available.
In the meantime, that's your chance to become famous - send your error reports 
to my mail address directly. (-v output may help, in some cases.)

Original issue reported on code.google.com by Steve8x8 on 25 Oct 2013 at 11:35

[GoogleCodeExporter]

I admit, I failed to backport ruby2.0 from Sid (unstable) to Wheezy (current 
stable), but I was able to unpack the 2.0.0p299 tarball, configure it 
(required: libssl-dev, openssl, bison, libreadline-dev) with 
--prefix=/usr/local, make, and make install. make check is still running...

To make a long story short: A first test (get all caches of Palestine) 
succeeded, and threw no error at all. Bad luck. So it's your turn now to hand 
in error reports (please include details about the Ruby version you've been 
using -> "ruby -v" will tell you).

Original comment by Steve8x8 on 25 Oct 2013 at 5:36

• Changed state: InfoNeeded

[GoogleCodeExporter]

Still, this seems to be a red herring to me - I have switched over to 2.0.0p299 
completely for my daily GeoToad usage, and haven't detected a single problem 
yet.
Perhaps this only shows up in a Windows environment? Time will tell as 3.18.2 
will come with an experimental Ruby 2.0 installer package... For the time 
being, I'm open for your contributions.

Original comment by Steve8x8 on 7 Nov 2013 at 10:24

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Bad news regarding the Windows Installer with Ruby 2.0.0: The Ocra gem isn't 
ready for the transition, and fails badly.
If you plan to use Windows with Ruby 2.0.0, get the tarball instead (this btw 
solves issue 287, too).

Original comment by Steve8x8 on 20 Nov 2013 at 1:05

[GoogleCodeExporter]

Updating the Ocra gem to 1.3.1 apparently resolved this issue... is there 
anything else (beyond issue 291) marking differences between ruby versions 
1.9.x and 2.0.0?

Original comment by Steve8x8 on 5 Dec 2013 at 8:49

• Changed state: Started

[GoogleCodeExporter]

I'm still hesitant to bump the Debian/Ubuntu dependencies so they include 
ruby2.0 ("ruby (>= 1.9.1)" might already include 2.0 for Jessie or the next 
Ubuntu release - who can tell me?

Original comment by Steve8x8 on 11 Dec 2013 at 12:17

• Changed state: InfoNeeded

[GoogleCodeExporter]

Windows (Ocra) support for 2.0.0 is there, and I haven't found any misbehaviour 
so far - actually I've been using 2.0.0 for a while now (it's rather 1.9.x that 
may cause problems...)
Closing.

Original comment by Steve8x8 on 22 Dec 2013 at 1:01

• Changed state: Fixed