isolate 1.0.0 → 1.0.1

data/CHANGELOG.rdoc

@@ -1,3 +1,8 @@
 === 1.0.0 / 2009-09-21
 
 * Birthday!
+
+=== 1.0.1 / 2009-09-21
+
+* Doco updates. [Review by Evan]
+* Don't modify Entry#options on install. [Review by Evan]

data/README.rdoc

@@ -4,9 +4,12 @@
 
 == Description
 
-Isolate is a very simple RubyGems sandbox. It restricts GEM_PATH and
-GEM_HOME, and provides a DSL for expressing your code's runtime Gem
-dependencies.
+Isolate is a very simple RubyGems sandbox. It provides a way to
+express and install your code's Gem dependencies.
+
+When Isolate runs, it uses GEM_HOME, GEM_PATH, and a few other tricks
+to completely separate your code from the system's RubyGems
+configuration, leaving it free to run in blissful solitude.
 
 While Isolate doesn't make any assumptions about what sort of code
 you're writing, it was extracted from a few Rails apps, so it's
@@ -18,7 +21,7 @@ full-featured Gem bundler, check out Yehuda Katz and Carl Lerche's
 Bundler[http://github.com/wycats/bundler]: It does a lot of fancy AOT
 dependency resolution, supports non-gem resources, and is probably a
 better fit for you. For a widely used Gem manager and installer, check
-out Chad Wooley's GemInstaller[http://geminstaller.rubyforge.org].
+out Chad Woolley's GemInstaller[http://geminstaller.rubyforge.org].
 
 YMMV, but I haven't tried Isolate with anything older than RubyGems
 1.3.5.
@@ -27,11 +30,11 @@ YMMV, but I haven't tried Isolate with anything older than RubyGems
 
 === Defining Your Isolated Environment
 
-The DSL's pretty easy: <tt>gem</tt> is similar to RubyGems'
-identically-named method. Version specifiers are optional, and any
-hash args tacked on to the end are passed through to
-Gem::DependencyInstaller as flags.
+It'spretty easy: <tt>gem</tt> is similar to RubyGems' method of the
+same name. Version specifiers are optional, and any hash args tacked
+on to the end are passed through to Gem::DependencyInstaller as flags.
 
+    require "rubygems"
     require "isolate"
 
     Isolate.gems "vendor/isolated" do
@@ -83,6 +86,7 @@ you want, you could just as easily put them in
 <tt>config/{gems,deps,whatever}.rb</tt>, just make sure it's loaded in
 the preinitializer:
 
+    require "rubygems"
     require "isolate"
 
     Isolate.gems "vendor/isolated", :install => true, :verbose => true do

data/lib/isolate.rb

@@ -7,7 +7,7 @@ require "rubygems/requirement"
 
 class Isolate
   Entry   = Struct.new :name, :requirement, :environments,  :options # :nodoc:
-  VERSION = "1.0.0" # :nodoc:
+  VERSION = "1.0.1" # :nodoc:
 
   attr_reader :entries # :nodoc:
 
@@ -166,10 +166,10 @@ class Isolate
         warn "#{progress} Isolating #{e.name} (#{e.requirement})."
       end
 
+      options     = e.options.dup.merge :install_dir => path
       old         = Gem.sources.dup
-      source      = e.options.delete :source
+      source      = options.delete :source
       Gem.sources = Array(source) if source
-      options     = e.options.merge :install_dir => path
       installer   = Gem::DependencyInstaller.new options
 
       installer.install e.name, e.requirement

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: isolate
 version: !ruby/object:Gem::Version 
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors: 
 - John Barnette
@@ -23,9 +23,12 @@ dependencies:
         version: 2.3.3
     version: 
 description: |-
-  Isolate is a very simple RubyGems sandbox. It restricts GEM_PATH and
-  GEM_HOME, and provides a DSL for expressing your code's runtime Gem
-  dependencies.
+  Isolate is a very simple RubyGems sandbox. It provides a way to
+  express and install your code's Gem dependencies.
+  
+  When Isolate runs, it uses GEM_HOME, GEM_PATH, and a few other tricks
+  to completely separate your code from the system's RubyGems
+  configuration, leaving it free to run in blissful solitude.
   
   While Isolate doesn't make any assumptions about what sort of code
   you're writing, it was extracted from a few Rails apps, so it's
@@ -37,7 +40,7 @@ description: |-
   Bundler[http://github.com/wycats/bundler]: It does a lot of fancy AOT
   dependency resolution, supports non-gem resources, and is probably a
   better fit for you. For a widely used Gem manager and installer, check
-  out Chad Wooley's GemInstaller[http://geminstaller.rubyforge.org].
+  out Chad Woolley's GemInstaller[http://geminstaller.rubyforge.org].
   
   YMMV, but I haven't tried Isolate with anything older than RubyGems
   1.3.5.