Closed GoogleCodeExporter closed 5 years ago
Release 3.21.0's Windows package comes with the latest Ruby 2.0 - as there's
still no 2.1 Ruby Installer for Windows available, due to one or two nasty
bugs. With those resolved, there will be two versions again, one based on 2.0,
one on 2.1 - stay tuned.
Original comment by Steve8x8
on 25 Jun 2014 at 5:31
As I don't have access to a constistent set of Ruby 2.1 versions for the
platforms to be supported, I strongly recommend to use 2.0 for now.
There has been a single report that ruby 2.1 behaves differently than previous
versions, resulting in the command line functionality to be broken. I cannot
reproduce this right now, and appreciate more details (which, I'm afraid, even
debug level 3 wouldn't present...) - volunteers, please step forward!
Original comment by Steve8x8
on 20 Aug 2014 at 6:58
Given that Debian has decided to make Squeeze a LTS (long-term support)
release, and there's only ruby 1.8 and 1.9 available for that, I currently tend
to freeze this issue.
Also the jump from 2.0 to 2.1 will not be made in a foreseeable future -
although Windows support for 2.1 has finally arrived a while ago.
For now, I'm running (= actively testing) on Wheezy - 1.9.3 on an ARM box, and
2.0.0 on my personal laptop; also there are infrequent test installations (but
usually no runs) on a Debian Jessie setup. I have little means to test Windows
or MacOSX packages.
Perhaps a time will come when I dig this issue out again, but probably not in
2015.
Original comment by Steve8x8
on 23 Jan 2015 at 10:34
Just a quick remark on the current state: As I'm still stuck with WinXP for building Windows Installer packages, and Ruby >= 2.1 lacks support for XP (due to a missing symbol in one of the system libraries) I will continue to build ruby 2.0 packages for a while. As soon as I can put my hands on a Win7 license I may setup a VM using that. This may take a couple of months. You say XP is outdated? Can't be, the trams here are still running on XP ;-) (well, rather the displays inside, but you never know)
In the not so far future, I'd like to experiment with Docker to handle both Windows and Mac builds. Anyone out there with a Docker 101 for me? Still got to find a suitable W. version - for MacOS, I've been pointed to "osxcross", not sure whether that will cover all my needs, and I don't have a machine to test the result. If you feel like it, step forward to assist. Thanks, S
Issue #326 (which has been caused by an incomplete handling of #322) seems to be related... Let's get rid of 1.9 soon, and of 2.0 soon thereafter.
3.25.0 (which has been flagged as the next Milestone) will require ruby >= 2.0, and recommend >= 2.1. Also, Windows XP support will be dropped, and the Windows Installer package will be created using Ruby >= 2.1.5 (which is now available for recent Windows versions). My next VM or build hardware (yet undecided) will be running Win 7, I won't be able to test Vista (does the 2.1 ruby-installer throw an error under Vista like it does under XP?)
After the migration of GC to https, and end-of-support for Windows XP, there's no real reason anymore to support Ruby <= 2.0 - the last version that worked with XP (and the VM that had been used to build the Windows Installer).
Yes, there will be no Win Installer anymore as long as I don't have access to a Win 7 VM. The last GeoToad release that came with a WI was 3.25.4.
The certificate chain will stay, but needs an update as well - or instructions how to get a recent version.
Windows users, please get your own Ruby installation (from rubyinstaller.org), get the GeoToad tarball and unpack it, and make sure you'll have the certificates in place - there are a few notes in the manual page (geotoad.pdf built from geotoad.1).
Ruby versions < 1.9.1 will result in an error, < 2.1.5 in a warning. Debian Stretch (9.5) has 2.3.3, Jessie (8.11) has 2.1.5 - no adverse effects have been found yet. Closing...
Original issue reported on code.google.com by
Steve8x8
on 17 Apr 2014 at 8:13