gemrage 0.1.1 → 0.1.2

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/exec

@@ -0,0 +1,33 @@
+
+∴ rvm exec some-command
+
+Executes arbitrary commands against rvm set operations. If given a set that
+matches a single ruby command, it will exec the command directly without printing
+out extra rvm information.
+
+Examples:
+
+To execute 'ruby -v' against all installed rubies and aliases, you would run:
+
+  ∴ rvm exec ruby -v
+
+If you instead want to execute it against a specific ruby (without extra logging
+/ data printed by rvm as is done with normal set operations), you can instead do:
+
+  ∴ rvm ree exec ruby -v
+
+Since it is a set operation, normal ruby specifiers will work. As an example, to run
+it against 1.9.2 and 1.8.7, you would run:
+
+  ∴ rvm 1.9.2,1.8.7 exec ruby -v
+
+Or, to execute 'gem env' against all gemsets:
+
+  ∴ rvm --with-rubies all-gemsets exec gem env
+
+To execute 'which ruby' in the current directory, loading a .rvmrc and falling back
+to the default ruby:
+
+  ∴ rvm --with-rubies default-with-rvmrc exec which ruby
+
+For more information, look up the rvm set operations.

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/fetch

@@ -0,0 +1,5 @@
+Fetch
+
+  Performs an archive / src fetch of the current selected ruby.
+
+Usage: ∴ rvm fetch

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/info

@@ -0,0 +1,64 @@
+
+∴ rvm info [ruby_string[,ruby_string[,...] [section,[section[,...]
+
+where sections are one of:
+
+  system rvm ruby homes binaries environment debug
+
+Both ruby strings and sections are optional arguments.
+
+By default with no parameters rvm info will output all sections except debug.
+
+To display system rvm debug information:
+
+  ∴ rvm debug
+
+which will display all sections including debug for the current or specified interpreters.
+
+Example:
+
+  ∴ rvm info 1.9.2-head,1.8.7 homes,binaries,environment
+
+  ruby-1.9.2-head:
+
+    homes:
+      gem:          "/Users/wayne/.rvm/gems/ruby-1.9.2-head"
+      ruby:         "/Users/wayne/.rvm/rubies/ruby-1.9.2-head"
+
+    binaries:
+      ruby:         "/Users/wayne/.rvm/rubies/ruby-1.9.2-head/bin/ruby"
+      irb:          "/Users/wayne/.rvm/rubies/ruby-1.9.2-head/bin/irb"
+      gem:          "/Users/wayne/.rvm/rubies/ruby-1.9.2-head/bin/gem"
+      rake:         "/Users/wayne/.rvm/gems/ruby-1.9.2-head/bin/rake"
+
+    environment:
+      GEM_HOME:     "/Users/wayne/.rvm/gems/ruby-1.9.2-head"
+      GEM_PATH:     "/Users/wayne/.rvm/gems/ruby-1.9.2-head:/Users/wayne/.rvm/gems/ruby-1.9.2-head@global"
+      BUNDLE_PATH:  "/Users/wayne/.rvm/gems/ruby-1.9.2-head"
+      MY_RUBY_HOME: "/Users/wayne/.rvm/rubies/ruby-1.9.2-head"
+      IRBRC:        "/Users/wayne/.rvm/rubies/ruby-1.9.2-head/.irbrc"
+      RUBYOPT:      ""
+      gemset:       ""
+
+  ruby-1.8.7-p249:
+
+    homes:
+      gem:          "/Users/wayne/.rvm/gems/ruby-1.8.7-p249"
+      ruby:         "/Users/wayne/.rvm/rubies/ruby-1.8.7-p249"
+
+    binaries:
+      ruby:         "/Users/wayne/.rvm/rubies/ruby-1.8.7-p249/bin/ruby"
+      irb:          "/Users/wayne/.rvm/rubies/ruby-1.8.7-p249/bin/irb"
+      gem:          "/Users/wayne/.rvm/rubies/ruby-1.8.7-p249/bin/gem"
+      rake:         "/Users/wayne/.rvm/gems/ruby-1.8.7-p249/bin/rake"
+
+    environment:
+      GEM_HOME:     "/Users/wayne/.rvm/gems/ruby-1.8.7-p249"
+      GEM_PATH:     "/Users/wayne/.rvm/gems/ruby-1.8.7-p249:/Users/wayne/.rvm/gems/ruby-1.8.7-p249@global"
+      BUNDLE_PATH:  "/Users/wayne/.rvm/gems/ruby-1.8.7-p249"
+      MY_RUBY_HOME: "/Users/wayne/.rvm/rubies/ruby-1.8.7-p249"
+      IRBRC:        "/Users/wayne/.rvm/rubies/ruby-1.8.7-p249/.irbrc"
+      RUBYOPT:      ""
+      gemset:       ""
+
+

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/migrate

@@ -0,0 +1,15 @@
+
+∴ rvm migrate from to
+
+Efficiently moves the gems from one ruby to another.
+Like 'rvm gemset copy' but removes the gems from the source
+ruby afterwards and runs it against all gemsets for a given
+ruby.
+
+Examples:
+
+To migrate all gemsets from rc2 of 1.9.2 to the first release, p0,
+you'd run:
+
+  ∴ rvm migrate 1.9.2-rc2 1.9.2-p0
+

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/rake

@@ -0,0 +1,14 @@
+Rake
+
+  RVM allows you to run rake tasks across multiple ruby versions, for example:
+
+    ∴ rvm 1.8.6,1.9.1 rake spec
+
+JSON Summary
+
+  Adding a --json flag prior to the word 'rake' and a JSON summary will be printed out at the end of the run.
+
+YAML Summary
+
+  Adding a --yaml flag prior to the word 'rake' and a YAML summary will be printed out at the end of the run.
+

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/repair

@@ -0,0 +1,23 @@
+
+∴ rvm repair {symlinks,environments,archives,all}
+
+Runs generate repair processes against given parts of rvm.
+
+Examples:
+
+To regenerate all of the environment files inside your rvm/environments
+directory, you'd run:
+
+  ∴ rvm repair environments
+
+To check for stale symlinks caused by rvm in your rvm_bin_path, you'd run:
+
+  ∴ rvm repair symlinks
+
+To verify all downloaded archives have the correct md5, you'd run:
+
+  ∴ rvm repair archives
+
+Or, to do all of the above, you'd run:
+
+  ∴ rvm repair all

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/ruby

@@ -0,0 +1,84 @@
+'rvm ruby'
+
+Given:
+
+∴ cat test.rb
+  puts "patchlevel: #{RUBY_PATCHLEVEL}, release_date: #{RUBY_RELEASE_DATE}, ruby_version: #{RUBY_VERSION}, ruby_platform: #{RUBY_PLATFORM}"
+
+∴ rvm list
+
+  ruby:
+
+     ruby-1.8.6-p383 [x86_64]
+     ruby-1.8.7-p174 [x86_64]
+     ruby-1.9.1-head [x86_64]
+  => ruby-1.9.1-p243 [x86_64]
+     ruby-1.9.2-preview3 [x86_64]
+
+  jruby:
+
+     jruby-1.3.1 [x86_64]
+     jruby-1.4.0RC3 [x86_64]
+
+  ree:
+
+     ree-1.8.6-20090610 [x86_64]
+     ree-1.8.7-20090928 [x86_64]
+
+
+We can run the ruby program 'test.rb' against all versions of ruby installed by RVM very simply:
+
+∴ rvm ruby test.rb
+
+    jruby-1.3.1: jruby 1.3.1 (ruby 1.8.6p287) (2009-06-15 2fd6c3d) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_15) [x86_64-java]
+
+    patchlevel: 287, release_date: 2009-06-15, ruby_version: 1.8.6, ruby_platform: java
+
+
+    jruby-1.4.0RC3: jruby 1.4.0RC3 (ruby 1.8.7 patchlevel 174) (2009-09-30 80c263b) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_15) [x86_64-java]
+
+    patchlevel: 174, release_date: 2009-09-30, ruby_version: 1.8.7, ruby_platform: java
+
+
+    ree-1.8.6-20090610: ruby 1.8.6 (2008-08-11 patchlevel 287) [i686-darwin10.0.0] Ruby Enterprise Edition 20090610
+
+    patchlevel: 287, release_date: 2008-08-11, ruby_version: 1.8.6, ruby_platform: i686-darwin10.0.0
+
+
+    ree-1.8.7-20090928: ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0], MBARI 0x6770, Ruby Enterprise Edition 20090928
+
+    patchlevel: 174, release_date: 2009-06-12, ruby_version: 1.8.7, ruby_platform: i686-darwin10.0.0
+
+
+    ruby-1.8.6-p383: ruby 1.8.6 (2009-08-04 patchlevel 383) [i686-darwin10.0.0]
+
+    patchlevel: 383, release_date: 2009-08-04, ruby_version: 1.8.6, ruby_platform: i686-darwin10.0.0
+
+
+    ruby-1.8.7-p174: ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0]
+
+    patchlevel: 174, release_date: 2009-06-12, ruby_version: 1.8.7, ruby_platform: i686-darwin10.0.0
+
+
+    ruby-1.9.1-head: ruby 1.9.2dev (2009-09-26 trunk 25103) [x86_64-darwin10.0.0]
+
+    patchlevel: -1, release_date: 2009-09-26, ruby_version: 1.9.2, ruby_platform: x86_64-darwin10.0.0
+
+
+    ruby-1.9.1-p243: ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-darwin10.0.0]
+
+    patchlevel: 243, release_date: 2009-07-16, ruby_version: 1.9.1, ruby_platform: i386-darwin10.0.0
+
+
+    ruby-1.9.2-preview3: ruby 1.9.2dev (2010-05-31 revision 28117) [x86_64-darwin10.3.0]
+
+    patchlevel: -1, release_date: 2010-05-31, ruby_version: 1.9.2, ruby_platform: x86_64-darwin10.3.0
+
+    ree-1.8.7-20090928: ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0], MBARI 0x6770, Ruby Enterprise Edition 20090928
+
+    patchlevel: 174, release_date: 2009-06-12, ruby_version: 1.8.7, ruby_platform: i686-darwin10.0.0
+
+If we want we can also restrict the above to a subset of named top level selections:
+
+  ∴ rvm 1.9.1,1.8.7,jruby test.rb
+    ...

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/rubygems

@@ -0,0 +1,11 @@
+
+∴ rvm rubygems [version]
+
+Installs a specific rubygems version in the current ruby. If
+current is specified, will install the most current rubygems
+as known by rvm.
+
+Please note that currently this is only compatible with ruby
+1.8.* and ruby enterprise edition. If your system isn't supported,
+running the command will generate an error message.
+

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/rvmrc

@@ -0,0 +1,34 @@
+
+∴ rvm rvmrc {trust,untrust,trusted,load,reset} [optional-path]
+
+Tools for dealing with and loading the rvmrc trust for a given directory.
+All actions take an optional path to a directory to check.
+
+Examples:
+
+To check the status of ~/My/project, you'd run:
+
+  ∴ rvm rvmrc trusted ~/My/project
+
+Or, more conventionally,
+
+  ∴ cd ~/My/project && rvm rvmrc trusted
+
+To manually set it as trusted:
+
+  ∴ rvm rvmrc trust ~/My/project
+
+Or, to reset the trust and force a prompt:
+
+  ∴ rvm rvmrc reset ~/My/project
+  
+Finally, to load the rvmrc in a directory, you'd run:
+
+  ∴ rvm rvmrc load ~/My/project
+
+Or,
+
+  ∴ cd ~/My/project && rvm rvmrc load
+  
+Note that this replaces 'rvm load-rvmrc'. Note that load implicity trusts the
+rvmrc, even if it is set to untrusted.

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/snapshot

@@ -0,0 +1,15 @@
+
+∴ rvm snapshot {load,save} filename
+
+Saves or creates a snapshot of the given rvm install. This includes:
+
+* Settings
+* Aliases
+* Rubies
+* Gemsets
+* Packages
+* Your Default
+
+Ideally to make it easy to have a consistent environment among machines
+/ to back up your environment. Please note that this is still considered
+experimental to a large degree.

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/tools

@@ -0,0 +1,22 @@
+
+∴ rvm tools {identifier,path-identifier,strings}
+
+Provides generic tools related to rvm environments for getting information
+about your current environment. Primarily used for scripting rvm.
+
+Examples:
+
+To get the expanded ruby string of the current environment, we'd run:
+
+  ∴ rvm tools identifier
+
+To get the identifier for a folder (taking into account rvmrc files and the like),
+we're instead run:
+
+  ∴ rvm tools path-identifier ~/path/to/directory
+
+Lastly, we can example ruby strings. E.g., to get the current ree version, we'd
+run:
+
+  ∴ rvm tools strings ree
+

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/upgrade

@@ -0,0 +1,18 @@
+
+∴ rvm upgrade ruby-prefix [optional-source]
+
+Attempts to install the latest version of a given ruby (still experimental).
+
+Given a ruby prefix (e.g. 1.9.2), it attempts to upgrade your last installed
+version, migrating gemsets.
+
+The process will prompt you at each stage - if the versions look incorrect,
+please cancel and perform it manually.
+
+Examples:
+
+If you have 1.9.2-rc2 installed and want to switch it to 1.9.2-p0,
+
+  ∴ rvm upgrade 1.9.2
+  
+Will install 1.9.2-p0 and migrate the gemsets.

data/vendor/ruby/1.8/gems/rvm-1.0.14/help/wrapper

@@ -0,0 +1,41 @@
+
+∴ rvm wrapper [ruby_string] [wrapper_prefix] [binary[ binary[ ...]]]
+
+Where ruby_string is the ruby version and gemset combination to wrap,
+wrapper prefix is what to prepend to the name of the generated wrapper
+binaries and binaries is the names of the binaries you wish to provide
+a wrapper for (e.g. gem).
+
+When no binaries are provided, rvm will by default generate wrappers for
+ruby, gem, rake, irb, rdoc, ri, and testrb.
+
+Examples:
+
+If you wish to provide an environment-specific wrapper for rspec with a
+rails 3 gemset, you could do:
+
+  ∴ rvm --create ree@rails3
+  ∴ rvm wrapper ree@rails3 r3 spec
+
+Which would add r3_spec with the specified environment to your the bin
+directory where you installed rvm.
+
+Alternatively, if you do:
+
+  ∴ rvm wrapper ruby-1.9.2-head
+
+It will create binaries named ruby,gem, rake, irb, rdoc, ri and tesrb
+in the rvm bin directory.
+
+Finally, to show another real and common use, you can use wrapper
+to generate ruby executables and gems for passenger to use. Namely:
+
+  ∴ rvm use ree@rails3 --passenger
+
+is equivelant to:
+
+  ∴ rvm use ree@rails3
+  ∴ rvm wrapper ree@rails3 passenger
+
+Which creates passenger_* binaries in the rvm bin directory using
+ree and the rails3 gemset.