Since I like to keep things clear we will create new directory which we will use when we launch pik_install command. It is recommended to avoid our ruby\bin directory.Ĭurrently our path contains directories added during Windows installation, directory where Git is installed and, finally, bin directory of our Ruby 2.2.1 version. The second one states that we must use pik_install command in order to install Pik, and we should pass it, as argument, some directory that is in the path. We are not upgrading Pik so we can skip the first one. Comments displayed after gem is installed are self-explanatory but let's analyze them. If you wonder where other gems come from when we didn't install them they are bundled with Ruby and are available with Ruby installation. Let's check that:Īs you can see Pik is available in the list of gems currently available to the default Ruby. 8.Ĭommand is executed in the new Command Prompt where the only Ruby available, at the moment, is 2.2.1, therefore gem will be installed in it. Installing RDoc documentation for pik -0. Located at: C: /ruby/IronRuby-091/bin > pik add C:\ruby\jruby -1. * If this is a first-time install, add all the versions of ruby that you want toĪdding: 186: ruby 1. * If you 're upgrading from a version path So in order to register Ruby version with Uru we have to execute uru admin add with a directory of Ruby's bin folder as an argument. Usage: admin add DIR | -recurse DIR | systemĮg: uru admin gem set init set install install uruĮg: uru admin retag 200p 197 200p 197-x 64 Open command prompt, go to target directory and execute following command:Īdd register an existing ruby installation In order to keep things isolated let's create new directory C:\tools and add it to the path as is explained in the first chapter - Windows Command Line. In order to install it you have to download archive with latest version from Bitbucket and unpack it in some folder that is in the PATH. Uru is new, lightweight, portable Ruby version manager which can be used to easily switch Ruby versions in the current Command Prompt. This certainly is not the most comfortable way and, fortunately, there is a much better solution. So we have to choose either to use Ruby in ConEmu's tabs or to constantly alter system path in order to change Ruby version we work with. Since we have used installer for the 2.2.1 and have chosen to add it to the path, in each Command Prompt we open it will be the only one available unless we add the path to the development version to the system path. The first one is official 2.2.1-p85 and the second one is the latest development version. Especially if we decide to install other Rubies besides MRI, like JRuby or IronRuby.Īt the moment we have two versions of Ruby on our system. Adding new Ruby version is somewhat complex and soon we might finish with too many different tabs in ConEmu so it would be hard to remember which tab corresponds to particular Ruby version. Testing scripts or running existing applications that relly on specific Ruby version require opening new or changing to tab that already has target Ruby activated. Even though we can use different Ruby versions this way, such approach has few drawbacks. Up to now we were managing multiple versions of Ruby through ConEmu tasks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |