On Mon, Mar 30, 2015 at 10:49 AM, leam hall <leamhall / gmail.com> wrote:

> This seems to be a common question. In this case, it is so the tool I'm
> writing actually gets used. My tool is for non-programmers. They will
> generally have neither the time nor inclination to use a tool that requires
> them to maintain a separate Ruby version.
>
> My tool supports a tool that embeds Ruby. Thus the only version of Ruby I
> can guarantee is available is that packaged version. That lets me lower the
> barrier to usage.
>
> So, really, support is secondary to usefulness.
>

Would bundling your own ruby with the tool work? See
https://www.ruby-toolbox.com/categories/packaging_to_executables for
options.

martin