geminstaller 0.2.1 → 0.2.2

data/History.txt

@@ -1,3 +1,7 @@
+== 0.2.2 / 2007-07-07
+* Fix performance problems with autogem command (don't manually recurse dependencies, gem method does it already)
+* Fix bad links in docs
+
 == 0.2.1 / 2007-06-07
 * Fixes to handle internal refactoring of command classes in RubyGems 0.9.3
 

data/Rakefile

@@ -78,7 +78,7 @@ task :website_rdocs => :docs do
   mv "doc", "website/output/code/rdoc"
 end
 
-desc "Generate ri locally for testing"
+desc "Generate website, including rdoc and coverage"
 task :website => [:webgen, :website_rdocs, :coverage] do
 end
 

data/TODO.txt

@@ -2,13 +2,14 @@
 * Allow array or eval'able string of gems to be passed as --gems arg or instead of args
 * Add @options[:gems], should be parsed from 
 =============== 0.2.4
-* Modify environment.rb for rails, not boot.rb.  Fix all doc references.
+* Understand environment.rb vs boot.rb.  Add doc references.
 * Catch permission errors, and print descriptive instructions on how to handle sudo.  "Uh Oh!  A gem installation failed because it did not have permission to write to the filesystem.  If you want to have automated GemInstaller goodness, you'll have to fix this.  Don't worry, it's easy!  You have three basic choices: ..."
 * docs - clean up sudo section.  Should be clearer about sudoers entry, and make sure that NOPASSWD is the last entry.
 * Faq - mention sudo
 * Faq - mention Zed's questions
 * design - dependency management is good.  Maven got it right, if not for the jelly...
 * search for config/geminstaller.yml by default
+* Investigate gem_plugin.  Plugin for mongrel???
 ================ 0.2.5 release ===================
 * Rename API: autogem -> gem, run -> install
 ================ 0.3.0 release =====================

data/lib/geminstaller/autogem.rb

@@ -3,39 +3,28 @@ module GemInstaller
     attr_writer :gem_command_manager, :gem_spec_manager, :gem_source_index_proxy
     def autogem(gems)
       @gem_source_index_proxy.refresh!
-      reversed_gems = gems.reverse!
       @completed_names = []
       @completed_gems = []
-      reversed_gems.each do |gem|
+      gems.each do |gem|
         process_gem(gem)
       end
       @completed_gems
     end
     
     def process_gem(gem)
+      p "Autogem#process_gem, gem: #{gem.name} - #{gem.version}"
       unless @completed_names.index(gem.name) or gem.no_autogem
         invoke_require_gem_command(gem.name, gem.version)
         @completed_names << gem.name
         @completed_gems << gem
       end
-      process_gem_dependencies(gem)
     end
     
-    def process_gem_dependencies(gem)
-      # TODO: this method is duplicated in rogue_gem_finder.  Should abstract and take a block
-      matching_gems = @gem_spec_manager.local_matching_gems(gem)
-      matching_gems.each do |matching_gem|
-        dependency_gems = @gem_command_manager.dependency(matching_gem.name, matching_gem.version.to_s)
-        dependency_gems.each do |dependency_gem|
-          process_gem(dependency_gem)
-        end
-      end
-    end
-
     def invoke_require_gem_command(name, version)
       if Gem::RubyGemsVersion.index('0.8') == 0
         require_gem(name, version)
       else
+        # TODO: should we check true/false result of gem method?
         gem(name, version)
       end
     end

data/lib/geminstaller.rb

@@ -29,7 +29,7 @@ module GemInstaller
   end
 
   def self.version
-    "0.2.1"
+    "0.2.2"
   end
 
   def self.create_application(args = [], registry = nil)

data/website/src/documentation/documentation.page

@@ -313,7 +313,7 @@ $ geminstaller --sudo # only use the -sudo option if necessary
 
 h3(#using_geminstaller_from_other_ruby_apps). Using GemInstaller from Other Ruby Apps
 
-If you want to automatically invoke GemInstaller from some other Ruby application, the approach will be very similar to the Rails approach shown above.  Instead of boot.rb, put the GemInstaller invocation into the class or script which is the very first one run when your application starts up.  To use it in build scripts such as <code>rake</code>, include it in a task.  GemInstaller (obviously) must run before any gems are loaded or referenced.
+If you want to automatically invoke GemInstaller from some other Ruby application, the approach will be very similar to the Rails approach "shown above":#invoking_geminstaller_from_rails.  Instead of boot.rb, put the GemInstaller invocation into the class or script which is the very first one run when your application starts up.  To use it in build scripts such as <code>rake</code>, include it in a task.  GemInstaller (obviously) must run before any gems are loaded or referenced.
 
 h2(#using_erb_in_config_files). Using <code>erb</code> in config files
 

data/website/src/index.page

@@ -38,5 +38,6 @@ Currently (as of version 0.0.2), the only _major_ known bug is related to auto-i
 
 h2(#history). History
 
+* 0.2.2 - Fix performance problems with autogem command (don't manually recurse dependencies, gem method does it already)
 * 0.2.1 - RubyGems release 0.9.3 had some major refactoring done to the internals, which broke GemInstaller 0.2.0.  GemInstaller 0.2.1 is a patch release to fix this.  I did limited testing on 0.9.3 and 0.9.0.  Please let me know if anything is broken on any version of RubyGems.
 * 0.2.0 - Initial release.  Yay!

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.9.4
 specification_version: 1
 name: geminstaller
 version: !ruby/object:Gem::Version 
-  version: 0.2.1
-date: 2007-06-07 00:00:00 -07:00
+  version: 0.2.2
+date: 2007-07-07 00:00:00 -07:00
 summary: GemInstaller provides automated management of RubyGems.
 require_paths: 
 - lib