Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

updated readme, post_install message, history.txt

  • Loading branch information...
commit 9a44481236dd42dd57320cfe02523ccefe28fc4b 1 parent 7bcd749
Gordon Thiesfeld authored
Showing with 36 additions and 23 deletions.
  1. +3 −1 History.txt
  2. +11 −11 README.rdoc
  3. +22 −11 Rakefile
4 History.txt
View
@@ -1,5 +1,7 @@
-=== 0.2.3 / 2009-XX-XX
+=== 0.2.3 / 2009-10-25
+* install improvements - better error message on unrecognized implementation, better version picking, better directory naming, renamed some variables to be more concise (not everything is a version - implementations have versions, and versions have packages)
+* added remote option to list command
* better error message when a version was deleted, but not removed from the config
* bugfix: run/gem/ruby command hangs when waiting for input
* renamed tools/pik.exe to pik_runner.exe to minimize confusion/conflicts
22 README.rdoc
View
@@ -60,23 +60,18 @@ Windows, more than one version of Ruby (otherwise, what's the point?) and Rubyge
== INSTALL:
-1. If you've used a version previous to this one, you'll need to uninstall them.
- Don't worry, this will leave your pik config intact.
+* If you're upgrading from a version <= 0.1.1, you'll want to delete the pik.bat file
+ from all of your ruby versions. Gem uninstall should do the trick.
- pik run "gem uninstall pik"
-
-2. Install the pik gem
-
- gem install pik
-
-3. You need to install pik to a location that's in your path, but someplace other than your ruby\bin dir
-
+* Install pik to a location that's in your path, but someplace other than your ruby\bin dir
+ If you're upgrading from a more recent version, pik_install will overwrite the older files as needed.
+
>path
PATH=C:\tools\;C:\ruby\186-p368-mingw32\bin;C:\WINDOWS\system32;C:\WINDOWS
>pik_install C:\tools
-4. Add all the versions of ruby that you want to use with pik
+* If this is a first-time install, add all the versions of ruby that you want to use with pik
>pik add
Adding: 186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
@@ -96,6 +91,11 @@ Note:
inside of the IronRuby lib:
pik config gem_home=C:\ruby\ironruby-091\lib\ironruby\gems\1.8
+
+ Also, if you're using a version of JRuby older than 1.4.0RC2, you'll probably need to set the JAVA_HOME env
+ variable.
+
+ set JAVA_HOME=C:\Program Files\Java\jre6
== EXAMPLES:
33 Rakefile
View
@@ -51,20 +51,31 @@ Hoe.spec('pik') do
----------------------------------------------------------------------------
-1. If you've used a version previous to this one, you'll need to uninstall them.
- Don't worry, this will leave your pik config intact.
+* If you're upgrading from a version <= 0.1.1, you'll want to delete the pik.bat file
+ from all of your ruby versions. Gem uninstall should do the trick.
- pik run "gem uninstall pik"
-
-2. Install the pik gem
-
- gem install pik
-
-3. You need to install pik to a location that's in your path, but someplace other than your ruby\\bin dir
+* Install pik to a location that's in your path, but someplace other than your ruby\\bin dir
+ If you're upgrading from a more recent version, pik_install will overwrite the older files as needed.
+
+ >path
+ PATH=C:\\tools\\;C:\\ruby\\186-p368-mingw32\\bin;C:\\WINDOWS\\system32;C:\\WINDOWS
- pik_install C:\\some\\other\\path
+ >pik_install C:\\tools
-4. Add all the versions of ruby that you want to use with pik
+* If this is a first-time install, add all the versions of ruby that you want to use with pik
+
+ >pik add
+ Adding: 186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
+ Located at: c:/ruby/186-p368-mingw32/bin
+
+ >pik add C:\\ruby\\IronRuby-091\\bin
+ Adding: 091: IronRuby 0.9.1.0 on .NET 2.0.0.0
+ Located at: C:/ruby/IronRuby-091/bin
+
+ >pik add C:\\ruby\\jruby-1.4.0RC1\\bin
+ Adding: 140: jruby 1.4.0RC1 (ruby 1.8.7 patchlevel 174) (2009-09-30 80c263b) (Java HotSpot(TM) Client VM 1.6.0_14) [x86-java]
+ Located at: C:/ruby/jruby-1.4.0RC1/bin
+
----------------------------------------------------------------------------
Please sign in to comment.
Something went wrong with that request. Please try again.