geminstaller 0.5.0 → 0.5.1

data/History.txt

@@ -1,3 +1,7 @@
+== 0.5.1 / yyyy-mm-dd
+* Print a very verbose and helpful error message if gem cannot be found on remote server.  Attempts to help http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/5-sometimes-installing-fails
+* Fix bug with stderr being swallowed silently when '--sudo' option is used.  
+
 == 0.5.0 / 2009-02-03
 * change default processing order of gems from alpha-version-platform to be order found in file (last config file wins).  Fixes http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/15-provide-a-way-to-specify-gem-processing-order .  Thanks to Brian Jenkins for helping!
 

data/Manifest.txt

@@ -7,8 +7,6 @@ README.txt
 Rakefile
 TODO.txt
 bin/geminstaller
-ci/README_CI.txt
-ci/cruise
 cruise_config.rb
 focused_spec.sh
 focused_spec_debug.sh

data/lib/geminstaller.rb

@@ -34,7 +34,7 @@ module GemInstaller
   end
 
   def self.version
-    "0.5.0"
+    "0.5.1"
   end
 
   def self.create_application(args = [], registry = nil)
@@ -91,7 +91,8 @@ module GemInstaller
       $stderr_backup = $stderr.dup
       $stderr.reopen("/dev/null", "w")
       io = IO.popen(cmd)
-      $stderr = $stderr_backup.dup
+      $stderr.reopen($stderr_backup)
+      STDERR.reopen($stderr_backup) # Why are these not the same?  It is an old question: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/47596
       output = io.read
       next unless output =~ /#{path_key}/
       path = output.sub(path_key,'')

data/lib/geminstaller/gem_list_checker.rb

@@ -15,7 +15,7 @@ module GemInstaller
       end
       
       if matched_lines.size > 1
-        error_message = "Error: more than one remote gem matches (this should not happen and is probably a bug in geminstaller).  Gem name = '#{gem.name}', install options = '#{gem.install_options}'.  Matching remote gems: \n"
+        error_message = "Error: more than one remote gem matches (this should not happen and is probably a bug in geminstaller).  Gem name = '#{gem.name}', install options = '#{gem.install_options.join(' ')}'.  Matching remote gems: \n"
         matched_lines.each do |line|
           error_message += line + "\n"
         end
@@ -23,7 +23,7 @@ module GemInstaller
       end
 
       if matched_lines.size == 0
-        error_message = "Error: Could not find remote gem to install.  Gem name = '#{gem.name}', Gem version = '#{gem.version}', install options = '#{gem.install_options}'"
+        error_message = "Error: Could not find remote gem to install.  Gem name = '#{gem.name}', Gem version = '#{gem.version}', install options = '#{gem.install_options.join(' ')}'.  Your remote gem server may be having problems.  You should try to list the remote gem yourself:  'gem list -r -v '#{gem.version}' #{common_args.join(' ')} #{gem.name}'.  If it exists on the server, try running geminstaller again and report your experience here: http://thewoolleyweb.lighthouseapp.com/projects/11580-geminstaller/tickets/5-sometimes-installing-fails.  Output of remote gem list command: \n#{remote_list}"
         raise GemInstaller::GemInstallerError.new(error_message)
       end
 

data/lib/geminstaller_rails_preinitializer.rb

@@ -4,7 +4,7 @@
 # or required in config/boot.rb before initialization for Rails < 2.0.  For example:
 #   require 'geminstaller_rails_preinitializer'
 #
-# If you require a different geminstaller configuration, copy this file into your Rails app,
+# If you require different geminstaller command options, copy this file into your Rails app,
 # modify it, and require your customized version.  For example:
 #   require "#{File.expand_path(RAILS_ROOT)}/config/custom_geminstaller_rails_preinitializer.rb"
 
@@ -17,7 +17,7 @@ module GemInstallerRailsPreinitializer
       args = ''
 
       # Specify --geminstaller-output=all and --rubygems-output=all for maximum debug logging
-      args += ' --geminstaller-output=all --rubygems-output=all'
+      # args += ' --geminstaller-output=all --rubygems-output=all'
 
       # The 'exceptions' flag determines whether errors encountered while running GemInstaller
       # should raise exceptions (and abort Rails), or just return a nonzero return code
@@ -30,6 +30,7 @@ module GemInstallerRailsPreinitializer
       #args += " --sudo" unless RUBY_PLATFORM =~ /mswin/
 
       # The 'install' method will auto-install gems as specified by the args and config
+      # IMPORTANT NOTE:  Under recent RubyGems versions, this will install to ~/.gem
       GemInstaller.install(args)
 
       # The 'autogem' method will automatically add all gems in the GemInstaller config to your load path,

data/website/src/documentation/documentation.page

@@ -29,6 +29,7 @@ h2. Table of Contents
 ** "<code>include_config</code> directive":#include_config
 * "Using GemInstaller with Ruby on Rails or Other Ruby Apps":#using_geminstaller_with_ruby_on_rails_or_other_ruby_apps
 ** "Invoking <code>GemInstaller</code> from Rails":#invoking_geminstaller_from_rails
+** "DEPRECATED Invoking <code>GemInstaller</code> from Rails 1.0":#invoking_geminstaller_from_rails_10
 ** "Bootstrapping Rails with GemInstaller":#bootstrapping_rails_with_geminstaller
 ** "Using GemInstaller from Other Ruby Apps":#using_geminstaller_from_other_ruby_apps
 * "Using <code>erb</code> in config files":#using_erb_in_config_files
@@ -268,7 +269,7 @@ gems:
 
 h2(#using_geminstaller_with_ruby_on_rails_or_other_ruby_apps). Using GemInstaller with Ruby on Rails or Other Ruby Apps
 
-GemInstaller can also be embedded in another application, such as a Rails app.  This is done by invoking the GemInstaller class or the geminstaller executable directly from Ruby.  This section only contains a brief explanation, see the tutorial on "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails for detailed explanation.
+GemInstaller can also be embedded in another application, such as a Rails app.  This is done by invoking the GemInstaller class or the geminstaller executable directly from Ruby.  Also see the tutorial on "Using GemInstaller with Ruby on Rails":index.html#using_geminstaller_with_ruby_on_rails .
 
 IMPORTANT NOTE: You need to know whether you run on unix and need root/sudo access to install gems and/or gem executables.  See "Dealing with sudo and root-owned RubyGem installations":#dealing_with_sudo section for more details.
 
@@ -276,7 +277,7 @@ First, you need to create <code>geminstaller.yml</code> in the <code>RAILS_ROOT/
 
 <pre><code>---
 defaults:
-  install_options: --include-dependencies
+  install_options: --no-ri --no-rdoc
 gems:
 - name: rails
   version: '= 1.1.6'
@@ -287,9 +288,36 @@ gems:
 
 h3(#invoking_geminstaller_from_rails). Invoking <code>GemInstaller</code> from Rails
 
-Once you have your *<code>geminstaller.yml</code>* created, invoke the GemInstaller on app startup in your boot.rb.  It should be placed right after the block which defines the RAILS_ROOT constant, as shown below ("..." indicates omitted lines):
+* Install the GemInstaller gem and create your *<code>config/geminstaller.yml</code>* config file.
 
-*RAILS_ROOT/config/boot.rb*:
+* Determine whether you run on unix and need root/sudo access to install gems.  If you do, edit your <code>sudoers</code> file to allow the current user to run the <code>'gem'</code> command via sudo without a password.  See the documentation on the GemInstaller "<code>--sudo</code> option":documentation.html#dealing_with_sudo for more details.
+
+* Create a <code>config/preinitializer.rb</code> file to invoke GemInstaller on your Rails app startup:
+
+*RAILS_ROOT/config/preinitializer.rb*:
+<pre><code>  require 'rubygems'
+  require 'geminstaller'
+  # You can use the geminstaller_rails_preinitializer out of the GemInstaller gem:
+  require 'geminstaller_rails_preinitializer'
+  # If you require different geminstaller command options, copy the geminstaller_rails_preinitializer.rb
+  # file into from the GemInstaller source into your Rails app, modify it, and require your customized 
+  # version.  For example:
+  # require "#{File.expand_path(RAILS_ROOT)}/config/custom_geminstaller_rails_preinitializer.rb"
+</code></pre>
+
+* Start your app: <code>ruby script/server</code>.  You should see (depending on verbosity level) messages indicating the gems (and dependency gems) are being installed and auto-required.
+* Stop the app, and verify the gems are installed: <code>gem list [some gem in your geminstaller.yml]</code>
+* For an example, check out the "Sample Rails App":http://geminstaller.rubyforge.org/svn/trunk/spec/fixture/sample_rails_app/ in the GemInstaller source.
+
+The default <code>geminstaller_rails_preinitializer.rb</code> in the GemInstaller source contains several comments which are hopefully self-explanatory.  See the "Command Line Options Summary":#command_line_options_summary, especially the "<code>--config</code>":#config_option, "<code>--exceptions</code>":#exceptions_option, and "<code>--sudo</code>":#sudo_option options for more details, as well as the "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails tutorial.
+
+h3(#invoking_geminstaller_from_rails_10). DEPRECATED - Invoking <code>GemInstaller</code> from Rails 1.0
+
+This section describes how to use GemInstaller with Rails 1.0 (which doesn't support config/preinitializer.rb).  If you are using Rails 2.0 or above, use "these instructions":#invoking_geminstaller_from_rails
+
+Once you have your *<code>geminstaller.yml</code>* created, invoke GemInstaller on Rails 1.0 startup in your boot.rb.  It should be placed right after the block which defines the RAILS_ROOT constant, as shown below ("..." indicates omitted lines):
+
+*RAILS_1.0_ROOT/config/boot.rb*:
 <pre><code>  ...
   unless defined?(RAILS_ROOT)
   ...
@@ -326,11 +354,9 @@ Once you have your *<code>geminstaller.yml</code>* created, invoke the GemInstal
   ...
 </code></pre>
 
-As you can see, this example contains several comments which are hopefully self-explanatory.  See the "Command Line Options Summary":#command_line_options_summary, especially the "<code>--config</code>":#config_option, "<code>--exceptions</code>":#exceptions_option, and "<code>--sudo</code>":#sudo_option options for more details, as well as the "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails tutorial.
-
 h3(#bootstrapping_rails_with_geminstaller). Bootstrapping Rails with GemInstaller
 
-If you don't already have Rails or Mongrel installed (you've just checked your app out or deployed onto a new machine), you obviously can't use the above boot.rb method to run GemInstaller.  In this case, you just need to run GemInstaller from the command line once to "bootstrap" and install the Rails/Mongrel gems.  This assumes you already have your <code>geminstaller.yml</code> config file in the Rails <code>config</code> dir:
+If you don't already have Rails or Mongrel installed (you've just checked your app out or deployed onto a new machine), you obviously can't use the above methods to run GemInstaller.  In this case, you just need to run GemInstaller from the command line once to "bootstrap" and install the Rails/Mongrel gems.  This assumes you already have your <code>geminstaller.yml</code> config file in the Rails <code>config</code> dir:
 
 <pre><code>
 $ cd [RAILS_APP_ROOT]/config
@@ -339,7 +365,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":#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.
+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 preinitializer.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
 
@@ -371,9 +397,9 @@ If you only run geminstaller on Windows, you don't have to worry about this sect
 
 <strong>UPDATE:</strong>
 
-After thinking about this problem a lot, I've become convinced the best way to "deal with sudo" is to never use it at all.  I've got a "feature planned":http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/1-automatically-create-use-and-manage-writeable-gem-home-if-system-gem-home-is-not-writeable that will address this issue, but still need to implement it.
+Probably the best way to "deal with sudo" is to never use it at all, and recent releases of RubyGems will automatically install gems to ~/.gem if you run gem install commands as a non-root user.  However, the RubyGems developers (Eric Hodel) have indicated that this feature may not remain, since it causes issues under Ruby 1.9.  I have a "feature":http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/1-automatically-create-use-and-manage-writeable-gem-home-if-system-gem-home-is-not-writeable to track the progress of this issue.
 
-<strong>FOR NOW, THOUGH:</strong>
+<strong>FOR NOW, THOUGH, HERE'S HOW TO USE SUDO WITH GEMINSTALLER:</strong>
 
 <strong>Important Note:</strong> For security, the sudo command does NOT pass most environment variables.  See the faq item on "Environment Variables and sudo":../faq.html#environment_vars_and_sudo for more info.
 
@@ -391,7 +417,7 @@ $ geminstaller -s
 $ geminstaller --sudo
 </code></pre>
 
-h3(#option_2). Option 2 - Run <code>sudo</code> or log in as root yourself
+h3(#option_2). Option 2 - Run <code>sudo</code> or log in as root yourself.  If you are running from a deploy script (Capistrano), this is probably the best option.
 
 Example of using sudo:
 <pre><code>

data/website/src/documentation/index.page

@@ -17,69 +17,36 @@ h2. Basic Usage - "Hello Doom"
 * Run GemInstaller from the directory containing geminstaller.yml: <code>geminstaller</code>.  You should see a message indicating that the gem is being installed.
 * Verify that the ruby-doom gem was installed: <code>gem list ruby-doom</code>
 
-h2. Using GemInstaller with Ruby on Rails
+h2(#using_geminstaller_with_ruby_on_rails). Using GemInstaller with Ruby on Rails
 
-<strong>RAILS 2.0 UPDATE:</strong>
+<strong>RAILS 2.0 INSTRUCTIONS:</strong>
 
-I've created a "Sample Rails App":http://geminstaller.rubyforge.org/svn/trunk/spec/fixture/sample_rails_app/ in the source, which shows how to use the Rails 2.0 config/preinitializer.rb hook.  I need to spend some time updating the docs to reflect this, but for now just "check out the source":http://geminstaller.rubyforge.org/svn/trunk/spec/fixture/sample_rails_app/
+* Follow the Basic Usage instructions above to install the GemInstaller gem and create a <code>config/geminstaller.yml</code> file in your Rails app's config directory
 
-<strong>OLD RAILS 1.0 INSTRUCTIONS:</strong>
+* Determine whether you run on unix and need root/sudo access to install gems.  If you do, edit your <code>sudoers</code> file to allow the current user to run the <code>'gem'</code> command via sudo without a password.  See the documentation on the GemInstaller "<code>--sudo</code> option":documentation.html#dealing_with_sudo for more details.
 
-* Create geminstaller.yml in the RAILS_ROOT/config directory.  Include entries for your Rails version, and any other gems your app needs (Note: If you are too lazy to make your config file manually, or don't know what gems you need, see the tutorial on "Bootstrapping your GemInstaller Config with the <code>--print-rogue-gems</code> option":tutorials.html#bootstrapping_your_geminstaller_config):
-<pre><code>  ---
-  # geminstaller.yml rails app config
-  defaults:
-    install_options: --include-dependencies
-  gems:
-  - name: rails
-    version: '= 1.1.6'
+* Create a <code>config/preinitializer.rb</code> file to invoke GemInstaller on your Rails app startup:
+
+*RAILS_ROOT/config/preinitializer.rb*:
+<pre><code>  require 'rubygems'
+  require 'geminstaller'
+  # You can use the geminstaller_rails_preinitializer out of the GemInstaller gem:
+  require 'geminstaller_rails_preinitializer'
+  # If you require different geminstaller command options, copy the geminstaller_rails_preinitializer.rb
+  # file into from the GemInstaller source into your Rails app, modify it, and require your customized 
+  # version.  For example:
+  # require "#{File.expand_path(RAILS_ROOT)}/config/custom_geminstaller_rails_preinitializer.rb"
 </code></pre>
 
+* Start your app: <code>ruby script/server</code>.  You should see (depending on verbosity level) messages indicating the gems (and dependency gems) are being installed and auto-required.
 
+* Stop the app, and verify the gems are installed: <code>gem list [some gem in your geminstaller.yml]</code>
 
-* Determine whether you run on unix and need root/sudo access to install gems.  If you do, edit your <code>sudoers</code> file to allow the current user to run the <code>'gem'</code> command via sudo without a password.  See the documentation on the GemInstaller "<code>--sudo</code> option":documentation.html#dealing_with_sudo for more details.
+* For an example, check out the "Sample Rails App":http://geminstaller.rubyforge.org/svn/trunk/spec/fixture/sample_rails_app/ in the GemInstaller source.
 
-* Edit your Rails <code>config/boot.rb</code> to invoke GemInstaller on startup to install gems and auto-require them.  The following lines should be placed right after the block which defines the RAILS_ROOT constant ("..." indicates omitted lines).  If you want to know what the heck this does before sticking it in your app, there are more details in the tutorial "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails
-<pre><code>  ---
-  RAILS_ROOT/config/boot.rb:
-  ...
-  unless defined?(RAILS_ROOT)
-  ...
-  end
- 
-  ############# Begin GemInstaller config - see http://geminstaller.rubyforge.org
-  require "rubygems"
-  require "geminstaller"
- 
-  # Path(s) to your GemInstaller config file(s)
-  config_paths = "#{File.expand_path(RAILS_ROOT)}/config/geminstaller.yml"
- 
-  # Arguments which will be passed to GemInstaller
-  args = "--config #{config_paths}"
- 
-  # The 'exceptions' flag determines whether errors encountered while running GemInstaller
-  # should raise exceptions (and abort Rails), or just return a nonzero return code
-  args += " --exceptions"
- 
-  # This will use sudo by default on all non-windows platforms, but requires an entry in your
-  # sudoers file to avoid having to type a password.  It can be omitted if you don't want to use sudo.
-  # See http://geminstaller.rubyforge.org/documentation/documentation.html#dealing_with_sudo
-  args += " --sudo" unless RUBY_PLATFORM =~ /mswin/
- 
-  # The 'install' method will auto-install gems as specified by the args and config
-  GemInstaller.install(args)
- 
-  # The 'autogem' method will automatically add all gems in the GemInstaller config to your load path, using the 'gem'
-  # or 'require_gem' command.  Note that only the *first* version of any given gem will be loaded.
-  GemInstaller.autogem(args)
-  ############# End GemInstaller config
- 
-  unless defined?(Rails::Initializer)
-  ...
-</code></pre>
+<strong>OLD RAILS 1.0 INSTRUCTIONS:</strong>
 
-* Start your app: <code>ruby script/server</code>.  You should see messages indicating the gems (and dependency gems) are being installed and auto-required.
-* Stop the app, and verify the gems are installed: <code>gem list rails</code>
+* See "Section on invoking GemInstaller from Rails 1.0":documentation.html#invoking_geminstaller_from_rails_10):
 
 h2. Where to go next
 

data/website/src/faq.page

@@ -3,9 +3,17 @@ title: FAQ
 ---
 h1. Frequently Asked Questions
 
+<span id="source_index_cannot_be_created_from_disk"/>
+Q: I got an error "source index cannot be created from disk"<br/>
+A: This is an incompatibility introduced in recent versions of RubyGems.  Upgrade to the latest version of GemInstaller.
+
+<span id="geminstaller_is_slow"/>
+Q: GemInstaller is taking FOREVER to run!<br/>
+A: First, run with the '-gall -rall' options to see all verbose output.  It is probably the underlying RubyGems command that is slow.  If you are on a version of RubyGems which is earlier than 1.2.0, there are know cache performance problems, and you should upgrade.  "This little script may help":http://gist.github.com/13223
+
 <span id="rails_config_gems"/>
 Q: Why not just use Rails' config.gems and rake tasks instead of GemInstaller?<br/>
-A: I'll come up with a feature comparison chart sometime.  For now, I'll mention a few reasons:  1) Rails itself cannot manage the Rails gems - but GemInstaller can via preinitializer.rb. 2) GemInstaller has more features that config.gems.  3) GemInstaller runs for any app or environment that needs to manage RubyGems, not just Rails.  Like Merb!  If you only use Rails, and none of these things matter to you, maybe you should consider using the Rails support :)
+A: A few reasons:  1) There are known issues with config.gems, since it attempts to load dependencies while the Rails environment is initializing, resulting in the possibility of "circular dependencies":http://groups.google.com/group/rubyonrails-core/browse_thread/thread/cffe26aaf784acf9/2480c6d27da36bd2.  GemInstaller does not have these issues when run from config/preinitializer.rb.  2) Rails itself cannot manage the Rails gems - but GemInstaller can via preinitializer.rb. 3) GemInstaller has more features that config.gems.  4) GemInstaller runs for any app or environment that needs to manage RubyGems, not just Rails.  See more discussion on "this rails core list thread":http://groups.google.com/group/rubyonrails-core/browse_thread/thread/cffe26aaf784acf9/2480c6d27da36bd2 or "this rails ticket":http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/59
 
 <span id="environment_vars_and_sudo"/>
 Q: Why can't I use environment variables via ERB in geminstaller.yml when using sudo?<br/>
@@ -15,7 +23,7 @@ Q: Why do some gems (like BlueCloth) always get reinstalled, even though they ar
 A: Dunno, this is either a bug in the gem or in RubyGems.  It isn't a problem with GemInstaller AFAIK, it happens even if you install manually via 'gem install'.  Haven't had time to debug, let me know if you figure it out.
 
 Q: What about gems like RMagick that have platform-specific binary dependencies?<br/>
-A: You are on your own, this is outside of the scope of GemInstaller.  The geminstaller.yml file is parsed with ERB, so you can put whatever hooks you want to perform necessary system setup and/or prereq validation.  You can also google or check the RMagick home page: "http://rmagick.rubyforge.org/":http://rmagick.rubyforge.org/
+A: You are on your own, this is outside of the scope of GemInstaller.  The geminstaller.yml file is parsed with ERB, so you can put whatever hooks you want to perform necessary system setup and/or prereq validation.  You can also google or check the RMagick home page: "http://rmagick.rubyforge.org/":http://rmagick.rubyforge.org/.  For Debian systems, check out the "AptInstaller":http://github.com/ngauthier/aptinstaller tool.
 
 Q: Why don't the tests/specs run on Windows?<br/>
 A: This has been improved with GemInstaller 0.3.0.  Using RubyGems 1.0.1 on Windows, install_smoketest.rb, autogem_smoketest.rb, and ruby test/test_all.rb all work.  See references to 'windows' on the "Code Page":code/index.html for more details.

data/website/src/index.page

@@ -24,7 +24,7 @@ It has been tested on all major platforms (mac, linux, windows), and has an "ext
 
 h2. How do I get it?
 
-GemInstaller can be "downloaded":http://rubyforge.org/frs/?group_id=1902 from RubyForge.
+GemInstaller can be installed with 'gem install geminstaller' or "downloaded":http://rubyforge.org/frs/?group_id=1902 from RubyForge.
 
 h2. How do I use it?
 
@@ -36,7 +36,7 @@ GemInstaller was created by "Chad Woolley":http://www.thewoolleyweb.com.
 
 h2. Why not just use Rails' config.gems?
 
-GemInstaller "has some advantages":faq.html#rails_config_gems over Rails' config.gems.
+GemInstaller "has advantages":faq.html#rails_config_gems over Rails' config.gems.
 
 h2(#known_issues). Known Issues
 
@@ -46,6 +46,9 @@ Please "report any others that you find":http://thewoolleyweb.lighthouseapp.com/
 
 h2(#history). History
 
+* 0.5.1
+** Print a very verbose and helpful error message if gem cannot be found on remote server.  Attempts to help "http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/5-sometimes-installing-fails":http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/5-sometimes-installing-fails
+** Fix bug with stderr being swallowed silently when '--sudo' option is used.  
 * 0.5.0
 ** change default processing order of gems from alpha-version-platform to be order found in file (last config file wins)
 * 0.4.5

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: geminstaller
 version: !ruby/object:Gem::Version 
-  version: 0.5.0
+  version: 0.5.1
 platform: ruby
 authors: 
 - Chad Woolley
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-02-03 00:00:00 -08:00
+date: 2009-02-23 00:00:00 -07:00
 default_executable: 
 dependencies: []
 
@@ -24,7 +24,6 @@ extra_rdoc_files:
 - Manifest.txt
 - README.txt
 - TODO.txt
-- ci/README_CI.txt
 files: 
 - .loadpath
 - COPYING
@@ -35,8 +34,6 @@ files:
 - Rakefile
 - TODO.txt
 - bin/geminstaller
-- ci/README_CI.txt
-- ci/cruise
 - cruise_config.rb
 - focused_spec.sh
 - focused_spec_debug.sh
@@ -129,9 +126,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: geminstaller
-rubygems_version: 1.3.1
+rubygems_version: 1.4.0
 signing_key: 
-specification_version: 2
+specification_version: 3
 summary: Automated Gem installation, activation, and much more!
 test_files: 
 - test/test_all.rb

data/ci/README_CI.txt

@@ -1,22 +0,0 @@
-Use these steps to run GemInstaller under CruiseControl.rb:
-
-* Create project with name 'geminstaller_using_rubygems_x-y-z', where 'x-y-z' is the version of RubyGems to test against.
-
-* symlink geminstaller/ci/cruise to /etc/init.d/cruise and follow instructions it contains to hook up init script and update-rc.d.
-
-* gem install mongrel and daemons (TODO: add these to geminstaller config)
-
-* Edit ~/.cruise/site_config.rb to have the following entries:
-
-# builds must run in serial for now, to prevent conflicts
-Configuration.serialize_builds = true
- 
-# use dedicated gmail account for mailing
-ActionMailer::Base.smtp_settings = {
-  :address =>        "smtp.gmail.com",
-  :port =>           587,
-  :domain =>         "thewoolleyweb.com",
-  :authentication => :plain,
-  :user_name =>      "thewoolleyweb.smtp",
-  :password =>       "????"
-}

data/ci/cruise

@@ -1,51 +0,0 @@
-#!/usr/local/bin/ruby
-
-ENV['PATH']="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11"
-
-# in order to make cruise run as daemon, you need:
-# 1. cp $CCRB_HOME/daemon/cruise.sample $CCRB_HOME/daemon/cruise
-# 2. specify your cruise_path to $CCRB_HOME in $CCRB_HOME/daemon/cruise file
-# 3. ln -s $CCRB_HOME/daemon/cruise /etc/init.d/cruise (you may need to 'sudo' this)
-# 4. update-rc.d cruise (you may want to choose options by yourself, and you may need to 'sudo' this)
-# 5. it's done :>
-
-require "fileutils"
-include FileUtils
-
-require "rubygems"
-
-begin
-  gem 'mongrel'
-rescue => e
-  puts "Error: daemon mode of CC.rb requires mongrel installed"
-  exit 1
-end
-
-def cruise_path
-  "/home/woolley/workspace/cruisecontrolrb"
-end
-
-def cruise_user
-  "woolley"
-end
-
-command = ARGV.shift
-
-case command
-when 'start'
-  #cd cruise_path
-  system "su - woolley -c 'cd #{cruise_path} && ./cruise start -d'"
-  exit 0
-when 'stop'
-  system "mongrel_rails stop -P #{cruise_path}/tmp/pids/mongrel.pid"
-  Dir["#{cruise_path}/tmp/pids/builders/*.pid"].each do |pid_file|
-    pid = File.open(pid_file){|f| f.read }
-    puts "Killing builder at file #{pid_file}, pid=#{pid}"
-    system "kill -9 #{pid}"
-    rm pid_file
-  end
-  exit 0
-else
-  p "Usage: /etc/init.d/cruise start|stop"
-  exit 1
-end