Issue #57 resolved

gemset: unable to find ruby specific when a tag might return multiple Rubies

Luis Lavena
created an issue

According to the docs uru admin gemset init takes a Ruby tag and @gemset option.

Problem is when you have two tags that are similar:

C:\Users\Luis\Code\_sandbox\foo>uru ls
    187p374     : ruby 1.8.7 (2013-06-27 patchlevel 374) [i386-mingw32]
    193p545     : ruby 1.9.3p545 (2014-02-24) [i386-mingw32]
    200p481     : ruby 2.0.0p481 (2014-05-08) [i386-mingw32]
    200p481-x64 : ruby 2.0.0p481 (2014-05-08) [x64-mingw32]

C:\Users\Luis\Code\_sandbox\foo>uru 200p481
---> these rubies match your `200p481` tag:

 [1] 200p481-x64 : ruby 2.0.0p481 (2014-05-08) [x64-mingw32]
                   Home: C:\Users\Luis\Tools\Ruby\ruby-2.0.0-p481-x64-mingw32\bin
 [2] 200p481     : ruby 2.0.0p481 (2014-05-08) [i386-mingw32]
                   Home: C:\Users\Luis\Tools\Ruby\ruby-2.0.0-p481-i386-mingw32\bin

select [1]-[2] to use that specific ruby (0 to exit) [0]: 2
---> Now using ruby 2.0.0-p481 tagged as `200p481`

C:\Users\Luis\Code\_sandbox\foo>uru admin gemset init 200p481@gemset
---> unable to find ruby specific to `200p481`; try again

Thank you.

Comments (1)

  1. jonforums repo owner

    Closing since current gemset support on master is a zombie. Initial bits were implemented, but support is truly non-functional. I'm about to swing back around and restart the effort on a new gemset branch.

  2. Log in to comment