VSI OpenVMS/I64 RUBY 2.2.2 or above distribution online location?

[Rod Regier]

Can someone please direct me to where I could download the VSI RUBY 2.2.2 (or higher) implementation for OpenVMS/I64?

It is mentioned as being available in Jun/2016 here:

https://vmssoftware.com/pdfs/VSI_Roadmap_20160603.pdf

Ruby is not in the VSI Layered Products Library media, which is reasonable for an available Open Source product.

Thanks

[Jan-Erik Soderholm]

The page says it has been "tested", as I interpret it. Not that it
has to be available from VSI. But you'd expect some kind of pointer
or link to where it is available, yes...

[Craig A. Berry]

It's probably not publicly available. It's easy to find under the open
source directory of the VSI sftp server if you have access to that.

[Jan-Erik Soderholm]

OK. We are close to have our Alpha support/licens agreement ready and
in some way we are to be given access to the ISO media files. Maybe
that is also through the "VSI sftp server". If so, I would also
expect that the OSS parts are available there.

A thought... If VSI puts time and money into testing/verifying OSS
kits for VMS, would it be reasonable that it is also required to
have a support agreement to get access to those kits for VMS?

[Rod Regier]

The Open Source section (page 6)+ in the linked document
in my initial posting has the title "Available" for Ruby and several other products.
Such nomenclature typically implies better access that simply "Tested".

re: Open Source products from VSI

I would prefer free, but I might be willing to pay.
So far I haven't seen any mechanism to acquire VSI Open Source Ruby 2.2.2
by *any* means.

[abrsvc]

I am checking with the appropriate individuals about the correct way to access the kit. I will update this with the info within the next day.

Dan

[Simon Clubley]

On 2017-06-06, Jan-Erik Soderholm <jan-erik....@telia.com> wrote:
>
> A thought... If VSI puts time and money into testing/verifying OSS
> kits for VMS, would it be reasonable that it is also required to
> have a support agreement to get access to those kits for VMS?
>

Not really.

I don't use Ruby, but two minutes of reading appears to show that Ruby
seems to have a dual licence so that doesn't apply to the following.

However, in the case of any products licenced under the GPL, all VSI can
control is the initial distribution and VSI are also required to make
any changes to the GPL source code available on request.

This is very reasonable IMHO, because VSI didn't write the GPL product
in the first place and they are seeing a benefit from it being available
on VMS.

VSI could take the Adacore approach of only making the initial
distribution available to paying customers, but they cannot then stop
any pure GPL code from then being distributed by those same customers.

The situation is comparable to RHEL and CentOS/Scientific Linux.

Red Hat didn't write the operating system and it's applications but
they are still receiving a financial benefit from packaging RHEL.
Therefore it is only fair that CentOS and Scientific Linux can use
Red Hat's packaging work to create a freely available CentOS and
Scientific Linux distribution.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world

[David Froble]

Personal opinion ....

Well, yes, and no.

Commercial users should have support.

Developers, hobbyists, and such, should have access, in some manner.

The key thing is, revenue should be from support, since it's recurring. But VMS
should be available to as wide an audience as possible. That's one way to get
more commercial users, and more revenue.

[abrsvc]

I received and was asked to post this from VSI:


Here is information you can use to download any and all VMS Software Inc. Open Source product kits.

Access Information:

Username: OPENKITS
Password: VSI#14kits <Case Sensitive>
Hostname: vsiftp.vmssoftware.com
IP Address: 104.207.199.163
Protocol : sftp


Please contact sup...@vmssoftware.com if you have issues accessing, downloading or installing files from the server..

sftp> ls
.
alpopensource << Alpha open source kits
i64java18apps << Applications that REQUIRE Java 1.8 , currently empty
i64opensource << Integrity Open Source kits
readme.txt
vsi_master_kit_list.txt

sftp> cd i64opensource << change to integrity folder

sftp> ls *ruby* << will list the ruby 2.2.2 kit

[Rod Regier]

Thanks abrsvc.

Directions worked great.

Successfully downloaded Ruby 2.2.2 ZIP set for I64.
It's a .PCSI binary kit inside.

Installed and ran on an RX2600 running patched HP V/I64 8.4

$ @SYS$STARTUP:RUBY$STARTUP.COM
$ ruby == "$SYS$SYSDEVICE:[VMS$COMMON.ruby.bin]ruby.exe "
$ ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [OpenVMS]

[lorin...@gmail.com]

Congrats, Rod, welcome to Ruby on VMS! I've been working with it for a while, and have developed a couple of com-file tricks that help make the use of Ruby scripts "a bit more natural" on VMS -- since DCL does not do shebang lines, there's naturally a few "gaps" to back-fill. You can fetch those com-files here (public repo) for review, use or derivations:

https://github.com/LorinRicker/VMScomfiles/

Nav into VMScomfiles/com/VMSruby for the command files themselves: RUBYCMD.COM and RUBY_SETUP.COM are the relevant/recommend ones, the others are just stash-copies of what's provided in VSI's Ruby distro.

This repo is a compendium of lots of scripts I use for teaching & support, not a nice, neat little "project/gem repo" like so many seem to favor now-a-days, but you're welcome to partake of any of it as you like. Any feedback is welcome, as are true forks and pull-requests. Hope this helps some. -- L