geminstaller 0.2.5 → 0.3.0

data/website/src/community/index.page

@@ -11,4 +11,4 @@ h2. Rubyforge Bug/Feature Tracker and Mailing Lists
 
 h2. Source Code
 
-* Subversion Repository: svn://rubyforge.org/var/svn/geminstaller/trunk
+* Subversion Repository:  "http://geminstaller.rubyforge.org/svn/trunk":http://geminstaller.rubyforge.org/svn/trunk

data/website/src/community/links.page

@@ -7,3 +7,5 @@ h1. Links
 ** "DiabeticMommy.com":http://www.diabeticmommy.com - Support site for women with diabetes, created and edited by Chad's wife
 * RubyGems
 ** "RubyGems Homepage":http://rubygems.org
+* RSpec
+** "RSpec Homepage":http://rspec.info/

data/website/src/documentation/documentation.page

@@ -25,7 +25,7 @@ h2. Table of Contents
 ** "<code>check_for_upgrade</code> config property":#check_for_upgrade_config_property
 ** "<code>fix_dependencies</code> config property":#fix_dependencies_config_property
 ** "<code>no_autogem</code> config property":#no_autogem_config_property
-** "<code>prefer_binary_platform</code> config property":#prefer_binary_platform_config_property
+** "<code>prefer_binary_platform</code> config property":#prefer_binary_platform_config_property (deprecated)
 ** "<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
@@ -119,8 +119,6 @@ h3(#redirect_stderr_to_stdout_option). <code>--redirect-stderr-to-stdout</code>
 
 Currently, the GemInstaller <code>--sudo</code> option works by recursively re-invoking the <code>geminstaller</code> executable via <code>system()</code>.  This option is automatically added in this case to ensure that errors that would normally go to <code>stderr</code> are printed to <code>stdout</code>.  There are other solutions to this problem, but as of Ruby 1.8.5, there is no _easy_ way to make a system call which will give a return code AND show both stderr and stdout _synchronously_.  GemInstaller does not have and will not have any third-party runtime dependencies, so I needed to roll my own solution, and this was The Simplest Thing That Could Possibly Work.
 
-When RubyGems supports platform specification from the command line, I won't have to select platforms programatically via stdin, and I'll be able to invoke <code>gem</code> directly via sudo.  Until then, though, there must be this recursive hackishness to handle sudo.
-
 h3(#geminstaller_output_option). <code>--geminstaller-output</code> option
 
 The <code>--geminstaller-output</code> option controls what GemInstaller prints out about it's internal activity.  It is a comma-delimited list (no spaces), which can specify any of these output types:
@@ -183,7 +181,7 @@ defaults:
   check_for_upgrade: [ true | FALSE ]
   fix_dependencies: [ true | FALSE ]
   no_autogem: [ true | FALSE ]
-  prefer_binary_platform:  [ TRUE | false ]
+  prefer_binary_platform:  [ TRUE | false ] (deprecated)
 gems:
 - name: [ gem name ]
   version: '[ any valid version specification for this gem, e.g. >= 1.0.0 ]'
@@ -196,6 +194,7 @@ gems:
 - name: [ another gem name ]
 - name: [ yet another gem name ]
   (etc...)
+<%= include_config("#{File.expand_path(File.dirname(__FILE__))}/path/to/included_snippet.yml") %>
 </pre>
 
 All properties are optional, except for the gem name.  If a default is specified, it will be used unless the gem specifically overrides it.
@@ -214,7 +213,7 @@ There are many different options for version specifications.  For more info, see
 
 h3(#platform_config_property). <code>platform</code> config property
 
-Defaults to 'ruby'.  This is the platform for the gem.  This must match a platform which is valid and available for the gem name and version specification.  See the sections on "Automatic Platform Detection":#automatic_platform_detection and the "<code>prefer_binary_platform</code> config property":#prefer_binary_platform for more info on how platforms are handled.
+Defaults to 'ruby'.  This is the platform for the gem.  This must match a platform which is valid and available for the gem name and version specification.  See the sections on "Automatic Platform Detection":#automatic_platform_detection and the "<code>prefer_binary_platform</code> config property":#prefer_binary_platform (deprecated) for more info on how platforms are handled.
 
 h3(#install_options_config_property). <code>install_options</code> config property
 
@@ -234,7 +233,9 @@ h3(#no_autogem_config_property). <code>no_autogem</code> config property
 
 Defaults to false.  This option will prevent the <code>autogem</code> command from automatically requiring a gem.  If you only want to require a few gems, you could set the default for this property to true, and only enable it (by setting a false value) for specific gems.  For more details see "Automatically Requiring Gems with the <code>autogem</code> Method":#automatically_requiring_gems_with_the_autogem_method.
 
-h3(#prefer_binary_platform_config_property). <code>prefer_binary_platform</code> config property
+h3(#prefer_binary_platform_config_property). <code>prefer_binary_platform</code> config property (deprecated)
+
+DEPRECATED:  This is deprecated when using RubyGems >= 0.9.5, which handles platform detection.
 
 Defaults to true.  GemInstaller automatically guesses at the correct platform for gem which have no platform specified.  Any platform which is not 'ruby' is considered a 'binary' platform.  
 
@@ -362,20 +363,22 @@ gems:
 
 h2(#automatic_platform_detection). Automatic Platform Detection
 
-Currently (as of version 0.9.2), RubyGems does not provide any way to specify a platform programatically or via the command line.  If the specified version of a gem has any binary or platform-specific releases, a list will be presented, and RubyGems will halt until input is provided via stdin.  This means that even if you write a script to install your required gems, you still have to deal with parsing the list and providing stdin input to select multi-platform gems.  To make it even more confusing, there are enforced requirements for what platforms are valid in a Gem specification file - the gem author can put whatever they want.  The RubyGems developers plan to deal with this situation in a future release, but until then...
+Up through version 0.9.4, RubyGems did not provide any way to specify a platform programatically or via the command line, and prompted via stdin if a specified version of a gem has any binary or platform-specific releases.  RubyGems 0.9.5 and later should correctly determine the correct platform to install, and GemInstaller will automatically use this feature.
 
-...GemInstaller solves this problem!  If a multi-platform gem version is found, GemInstaller will handle the list prompt, and automatically select the correct platform.
+However, if you must run older versions of RubyGems <= 0.9.4, GemInstaller still includes support for automatically selecting the platform without any stdin prompts.  If a multi-platform gem version is found, GemInstaller will handle the list prompt, and automatically select the correct platform.
 
-The "correct" platform can be determined in a few ways.  The easiest way is to let GemInstaller guess at the platform for you.  It contains logic which will attempt to determine the correct platform to choose, based on the platform of the current machine.
+This means that you don't have to worry about what version of RubyGems your app will run on - GemInstaller handles automatic platform selection on all RubyGems versions.
 
-However, GemInstaller may not always guess right, especially for uncommon platforms, or gems which do not have a standard platform string specified.  In these cases, the <code>'platform'</code> property for a gems can be specified in the geminstaller config file.  If you know what platform you want for a specific gem, and you only run GemInstaller on one platform, you can hardcode this value.  Even if you run GemInstaller on multiple platforms (and therefore can't hardcode the platform string), you can use <code>erb</code> to programatically pick the correct platform.  See "Using <code>erb</code> in config files":#using_erb_in_config_files for an example.
+If you do want explicit control over the platform which is used, all you need to do is specify the <code>'platform'</code> property for any multiplatform gems can be specified in the geminstaller config file.  If you know what platform you want for a specific gem, and you only run GemInstaller on one platform, you can hardcode this value.  Even if you run GemInstaller on multiple platforms (and therefore can't hardcode the platform string), you can use <code>erb</code> to programatically pick the correct platform.  See "Using <code>erb</code> in config files":#using_erb_in_config_files for an example.
 
-See the section on the "<code>prefer_binary_platform</code> config property":#prefer_binary_platform for more info.
+See the section on the "<code>prefer_binary_platform</code> config property":#prefer_binary_platform_config_property (deprecated) for more info.
 
 h2(#dealing_with_sudo). Dealing with sudo and root-owned RubyGem installations 
 
 If you only run geminstaller on Windows, you don't have to worry about this section :)
 
+<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.
+
 On many unix-like systems (Mac, Linux, etc.), the root user will own the local installation of RubyGems (often /usr/local/ruby) and/or the executable directory where gem executables are installed (often /usr/local/bin).  If this is the case, then gems must be installed and uninstalled by the root user, or via the sudo command.  This presents a problem for geminstaller, which must have this same permission to automatically install gems.
 
 There are several different solutions this problem.  The solutions that are available are also determined by the way you use geminstaller (whether you call it from the executable, or use the GemInstaller classes directly from Ruby).

data/website/src/documentation/tutorials.page

@@ -8,7 +8,7 @@ If anything is unclear, or if you'd like to see a tutorial on a topic, please su
 * "Bootstrapping your GemInstaller Config with the <code>--print-rogue-gems</code> option":#bootstrapping_your_geminstaller_config
 * "Using the <code>autogem</code> Option to Automatically Require Gems":#using_the_autogem_option_to_automatically_require_gems
 * "Integrating GemInstaller into Ruby on Rails":#integrating_geminstaller_into_ruby_on_rails
-* "Using Common or Shared Config Files":#using_common_or_shared_config_files
+* "Using Common or Shared Config Files or Snippets":#using_common_or_shared_config_files
 * "Running GemInstaller from Capistrano":#running_geminstaller_from_capistrano
 
 h2(#installing_geminstaller). Installing GemInstaller
@@ -33,10 +33,10 @@ That was easy, wasn't it?  This config file should specify the exact versions fo
 
 Gotchas/Notes:
 
-# If you generated the file on a unix/mac system with compiled gems and then try to run it on a different platform (like windows) which does not have a compiler, you may get errors.  The "<code>prefer_binary_platform</code> config property":documentation.html#prefer_binary_platform_config_property will try to guess at the correct platform, but if a binary version of the gem does not exist for your platform, or if <code>prefer_binary_platform</code> fails to guess the right platform, you may still fail.
+# If you generated the file on a unix/mac system with compiled gems and then try to run it on a different platform (like windows) which does not have a compiler, you may get errors.  The "<code>prefer_binary_platform</code> config property":documentation.html#prefer_binary_platform_config_property (deprecated) will try to guess at the correct platform, but if a binary version of the gem does not exist for your platform, or if <code>prefer_binary_platform</code> fails to guess the right platform, you may still fail.
 # The <code>--print-rogue-gems</code> option generates *exact* version specifications.  This means that you won't ever get any gem upgrades by running GemInstaller with the standard generated file.  This may be good (an upgrade can never break your app unexpectedly).  However, you may wish to modify some of the version specifications to allow for upgrades.  If you do this, remember to set the "<code>check_for_upgrade</code> config property":documentation.html#check_for_upgrade_config_property to true, but be aware that this will cause GemInstaller to check the remote gem server for upgrades each time it runs, and cause it to run slow or fail if the server is unavailable.    
 
-See also: Docs on "<code>--print-rogue-gems</code> option":documentation.html#print_rogue_gems_option, "<code>prefer_binary_platform</code> config property":documentation.html#prefer_binary_platform_config_property, and "<code>check_for_upgrade</code> config property":documentation.html#check_for_upgrade_config_property
+See also: Docs on "<code>--print-rogue-gems</code> option":documentation.html#print_rogue_gems_option, "<code>check_for_upgrade</code> config property":documentation.html#check_for_upgrade_config_property, and "<code>prefer_binary_platform</code> config property":documentation.html#prefer_binary_platform_config_property (deprecated).
 
 h2(#using_the_autogem_option_to_automatically_require_gems). Using the <code>autogem</code> Option to Automatically Require Gems option
 
@@ -76,7 +76,7 @@ h2(#integrating_geminstaller_into_ruby_on_rails). Integrating GemInstaller into
 
 GemInstaller can be configured to automatically install all gems in the config file, and add them to the load path when Rails boots.  This means that you can check out and run your application anywhere, without having to worry about manually ensuring that the required dependency gems are installed.  This works with Webrick and Mongrel.
 
-IMPORTANT NOTE:  Currently, there is a bug with installing Mongrel and Rails gems on Rails startup.  See "Known Bugs":../index.html#known_bugs for details.
+IMPORTANT NOTE:  Currently, there is an issue with installing Mongrel and Rails gems on Rails startup (the old versions are already on the LOAD_PATH, so a restart is required to pick up the new ones).  See "Known Issues":../index.html#known_issues for details.
 
 First, you need a Rails app.  I'll let you handle this step on your own.  See the "Rails documentation":http://www.rubyonrails.org/docs for details.
 
@@ -272,17 +272,23 @@ That's about it!
 See also: Docs on "Using GemInstaller with Ruby on Rails or Other Ruby Apps":documentation.html#using_geminstaller_with_ruby_on_rails_or_other_ruby_apps. 
 
 
-h2(#using_common_or_shared_config_files). Using Common or Shared Config Files
+h2(#using_common_or_shared_config_files). Using Common or Shared Config Files or Snippets
 
-GemInstaller supports multiple config files, with the last config files in the list overriding the previous ones.  This means you could do any of the following:
+GemInstaller supports multiple config files, with the last config files in the list overriding the previous ones.  It also supports the "<code>include_config</code>":documentation.html#include_config property in the <code>geminstaller.yml</code> file, which allows you to share a YAML snippet across multiple config files.  This means you could do any of the following:
 
-* Have a common config file across all your projects, which is shared via an svn:external, and a custom config file to override or add gems which are not in the common config.
-* Have a common config file across all development machines, shared on a windows share or NFS mounted drive, with machine- or platform-specific gems listed in local config files.
-* Have config files that are specific to certain environments such as development and test, which will not be included when GemInstaller is run in a demo or production environment.
+* With multiple config files:
+** Have a common config file across all your projects, which is shared via an svn:external, and a custom config file to override or add gems which are not in the common config.
+** Have a common config file across all development machines, shared on a windows share or NFS mounted drive, with machine- or platform-specific gems listed in local config files.
+** Have config files that are specific to certain environments such as development and test, which will not be included when GemInstaller is run in a demo or production environment.
+* With the "<code>include_config</code>":documentation.html#include_config property:
+** Shared YAML snippets across multiple geminstaller.yml files via an svn:external.
+** Extract geminstaller.yml entries that are duplicated across multiple files to a single shared include snippet file.
+** Use a common include to simultaneously upgrade to the same version of a gem dependency across multiple projects.
+** Extract complicated or shared ERB logic in geminstaller.yml (such as automatically determining the correct version of a gem based on an environment variable) into a separate file. 
 
 TODO: Finish writing examples of this, for now see docs on the "<code>--config</code>":documentation.html#config_option option. 
 
-See also: Docs on the "<code>--config</code>":documentation.html#config_option option. 
+See also: Docs on the "<code>--config</code>":documentation.html#config_option option, Docs on the "<code>include_config</code>":documentation.html#include_config property. 
 
 
 h2(#running_geminstaller_from_capistrano). Running GemInstaller from Capistrano

data/website/src/faq.page

@@ -3,5 +3,20 @@ title: FAQ
 ---
 h1. Frequently Asked Questions
 
+
+<span id="environment_vars_and_sudo"/>
+Q: Why can't I use environment variables via ERB in geminstaller.yml when using sudo?<br/>
+A: For security, the sudo command does NOT pass most environment variables.  That means if you are trying to use an environment variable to control logic in your geminstaller.yml (for example to dynamically specify a gem version), then it won't work!  I don't yet have a good workaround for this, other than not using sudo.  I may add an option to auto-parse environment variables from the command line, like Rake.  Let me know if you have ideas.
+
+Q: Why do some gems (like BlueCloth) always get reinstalled, even though they are already installed?<br/>
+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/
+
 Q: Why don't the tests/specs run on Windows?<br/>
 A: Dunno, something with the process handling on windows for TestGemHome and EmbeddedGemServer.  The manual application tests under spec/smoketest/ work on windows, though.
+
+
+<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>This space intentionally left blank.<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
+

data/website/src/index.page

@@ -10,15 +10,16 @@ GemInstaller provides automated management of RubyGems.  It uses a simple YAML c
 * Automatically install the correct versions of all required gems wherever your app runs.
 * Automatically ensure installed gems and versions are consistent across multiple applications, machines, platforms, and environments 
 * Automatically add correct versions of gems to the ruby load path when your app runs ('require_gem'/'gem')
-* Automatically reinstall missing dependency gems
-* Automatically guess at correct platform to install for multi-platform gems
+* Automatically reinstall missing dependency gems (built in to RubyGems > 1.0)
+* Automatically detect correct platform to install for multi-platform gems (built in to RubyGems > 1.0)
 * Print YAML for "rogue gems" which are not specified in the current config, to easily bootstrap your config file, or find gems that were manually installed without GemInstaller.
-* Allow for common configs to be reused across projects or environments by supporting multiple config files and defaults with overrides.
+* Allow for common configs to be reused across projects or environments by supporting multiple config files, including common config file snippets, and defaults with overrides.
+* Allow for dynamic selection of gems, versions, and platforms to be used based on environment vars or any other logic.
 * Avoid the "works on demo, breaks on production" syndrome
 
 GemInstaller can be used from the command line, or embedded to run automatically on startup for a Rails app or any other Ruby program.
 
-It has been tested on all major platforms (mac, linux, windows), and recent versions of RubyGems (0.8.x through 0.9.4).
+It has been tested on all major platforms (mac, linux, windows), and has an "extensive suite of tests":code/coverage/index.html which are "automatically run by Continuous Integration":http://ci.thewoolleyweb.com against recent versions of RubyGems (0.8.x through 1.0.1)..
 
 h2. How do I get it?
 
@@ -32,14 +33,27 @@ h2. Who is responsible for GemInstaller?
 
 GemInstaller was created by "Chad Woolley":http://www.thewoolleyweb.com.
 
-h2(#known_bugs). Known Bugs
+h2(#news). News
 
-Currently, the only _major_ known bug is related to auto-installing the Rails or Mongrel gems via boot.rb during startup of Mongrel or Webrick.  The simple workaround is to run GemInstaller manually or just restart Rails anytime GemInstaller auto-installs a Rails/Mongrel gem upgrade during app startup.  For Rails and other deployable apps, you can also "run GemInstaller from Capistrano":documentation/tutorials.html#running_geminstaller_from_capistrano to avoid this problem in demo/production environments.  I bet there's another bug or twoo, so please "report them if you find them":http://rubyforge.org/tracker/?group_id=1902!
+Version 0.3.0 of GemInstaller is released.  This is tested and working against latest RubyGems 1.0.1.
 
-There's also some leakage of gem doc warning messages even if you turn down --rubygems-output, but these can be ignored (these same messages show up when installing gems manually).  This should be fixed soon.
+h2(#known_issues). Known Issues
+
+Currently, the only _major_ known issue is related to auto-installing the Rails or Mongrel gems via boot.rb or config/preinitializer.rb during startup of Mongrel or Webrick.  This is because the old version is already on the load path before GemInstaller installs the new version.  The simple workaround is to just restart Rails anytime GemInstaller auto-installs a Rails/Mongrel gem upgrade during app startup.  For Rails and other deployable apps, you can also "run GemInstaller from Capistrano":documentation/tutorials.html#running_geminstaller_from_capistrano to avoid this problem in demo/production environments.
+
+There's also some leakage of gem doc warning messages even if you turn down --rubygems-output, but these can be ignored (these same messages can show up when installing gems manually).
+
+I bet there's another bug or twoo, so please "report them if you find them":http://rubyforge.org/tracker/?group_id=1902!
 
 h2(#history). History
 
+* 0.3.0
+** Changes to work with RubyGems >= 0.9.5 and take advantage of new platform and auto-install features.  See "notes on RubyGems version compatibility":code/index.html#rubygems_compatibility
+** On Linux/Mac, you can now specify a RUBYGEMS_VERSION environment var to test against a specific version of RubyGems.
+** Improved smoketest.rb and autogem_test.rb
+** Tests now run on windows (only against latest rubygems, with it installed, and only via test/test_all.rb, not rake)
+** deprecated/disabled prefer_binary_platform
+** many other small cleanups
 * 0.2.5
 ** Add 'include_config' directive to yaml config file, allowing other files to be included via ERB.
 ** Fix broken links in docs - patch from  Maciej Kozak (macio)

metadata

@@ -1,33 +1,30 @@
 --- !ruby/object:Gem::Specification 
-rubygems_version: 0.9.4
-specification_version: 1
 name: geminstaller
 version: !ruby/object:Gem::Version 
-  version: 0.2.5
-date: 2007-10-24 00:00:00 -07:00
-summary: GemInstaller provides automated management of RubyGems.
-require_paths: 
-- lib
-email: ryand-ruby@zenspider.com
-homepage: "    by Chad Woolley"
-rubyforge_project: geminstaller
-description: "== FEATURES:  GemInstaller provides automated management of RubyGems.  It uses a simple YAML config file to:  * Automatically install the correct versions of all required gems wherever your app runs. * Automatically ensure installed gems and versions are consistent across multiple applications, machines, platforms, and environments  * Automatically add correct versions of gems to the ruby load path when your app runs ('require_gem'/'gem') * Automatically reinstall missing dependency gems * Automatically guess at correct platform to install for multi-platform gems * Print YAML for \"rogue gems\" which are not specified in the current config, to easily bootstrap your config file, or find gems that were manually installed without GemInstaller. * Avoid the \"works on demo, broken on production\" syndrome  == SYNOPSYS:  GemInstaller provides automated management of RubyGems."
-autorequire: 
-default_executable: 
-bindir: bin
-has_rdoc: true
-required_ruby_version: !ruby/object:Gem::Version::Requirement 
-  requirements: 
-  - - ">"
-    - !ruby/object:Gem::Version 
-      version: 0.0.0
-  version: 
+  version: 0.3.0
 platform: ruby
-signing_key: 
-cert_chain: 
-post_install_message: 
 authors: 
 - Chad Woolley
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2008-01-01 00:00:00 -07:00
+default_executable: 
+dependencies: []
+
+description: "== FEATURES:  GemInstaller provides automated management of RubyGems.  It uses a simple YAML config file to:  * Automatically install the correct versions of all required gems wherever your app runs. * Automatically ensure installed gems and versions are consistent across multiple applications, machines, platforms, and environments  * Automatically add correct versions of gems to the ruby load path when your app runs ('require_gem'/'gem') * Automatically reinstall missing dependency gems (built in to RubyGems > 1.0) * Automatically detect correct platform to install for multi-platform gems (built in to RubyGems > 1.0) * Print YAML for \"rogue gems\" which are not specified in the current config, to easily bootstrap your config file, or find gems that were manually installed without GemInstaller. * Allow for common configs to be reused across projects or environments by supporting multiple config files, including common config file snippets, and defaults with overrides. * Allow for dynamic selection of gems, versions, and platforms to be used based on environment vars or any other logic. * Avoid the \"works on demo, breaks on production\" syndrome  == SYNOPSYS:  GemInstaller provides automated management of RubyGems."
+email: ryand-ruby@zenspider.com
+executables: 
+- geminstaller
+extensions: []
+
+extra_rdoc_files: 
+- History.txt
+- Manifest.txt
+- README.txt
+- TODO.txt
+- ci/README_CI.txt
 files: 
 - .loadpath
 - COPYING
@@ -38,7 +35,11 @@ files:
 - Rakefile
 - TODO.txt
 - bin/geminstaller
-- ci/cruisecontrol
+- ci/README_CI.txt
+- ci/cruise
+- cruise_config.rb
+- focused_spec.sh
+- focused_spec_debug.sh
 - geminstaller.yml
 - lib/geminstaller.rb
 - lib/geminstaller/application.rb
@@ -52,7 +53,6 @@ files:
 - lib/geminstaller/exact_match_list_command.rb
 - lib/geminstaller/file_reader.rb
 - lib/geminstaller/gem_arg_processor.rb
-- lib/geminstaller/gem_command_line_proxy.rb
 - lib/geminstaller/gem_command_manager.rb
 - lib/geminstaller/gem_interaction_handler.rb
 - lib/geminstaller/gem_list_checker.rb
@@ -76,6 +76,7 @@ files:
 - lib/geminstaller/rubygems_exit.rb
 - lib/geminstaller/rubygems_extensions.rb
 - lib/geminstaller/rubygems_version_checker.rb
+- lib/geminstaller/source_index_search_adapter.rb
 - lib/geminstaller/unauthorized_dependency_prompt_error.rb
 - lib/geminstaller/unexpected_prompt_error.rb
 - lib/geminstaller/valid_platform_selector.rb
@@ -97,21 +98,32 @@ files:
 - website/src/download.page
 - website/src/faq.page
 - website/src/index.page
-test_files: 
-- test/test_all.rb
+has_rdoc: true
+homepage: "    by Chad Woolley"
+post_install_message: 
 rdoc_options: 
 - --main
 - README.txt
-extra_rdoc_files: 
-- History.txt
-- Manifest.txt
-- README.txt
-- TODO.txt
-executables: 
-- geminstaller
-extensions: []
-
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
 requirements: []
 
-dependencies: []
-
+rubyforge_project: geminstaller
+rubygems_version: 1.0.1
+signing_key: 
+specification_version: 2
+summary: GemInstaller provides automated management of RubyGems.
+test_files: 
+- test/test_all.rb

data/ci/cruisecontrol

@@ -1,50 +0,0 @@
-CRUISECONTROL_DIR=/home/woolley/workspace/geminstaller_ci
-CRUISECONTROL_CMD=$CRUISECONTROL_DIR/cruise
-PIDFILE=/tmp/cruisecontrol.pid
-
-if [ "$CRUISECONTROL_USER" = "" ] ; then
-  CRUISECONTROL_USER=cruisecontrol
-fi
-
-if [ "$JAVA_HOME" = "" ] ; then
-  export JAVA_HOME=/usr/java/jdk
-fi
-export PATH=$PATH:$JAVA_HOME/bin
-
-case "$1" in
-  start)
-    echo -n "Starting CruiseControl"
-    cd $CRUISECONTROL_DIR
-    start-stop-daemon --start --pidfile $PIDFILE --make-pidfile --user $CRUISECONTROL_USER --chuid $CRUISECONTROL_USER --chdir /home/woolley/workspace/geminstaller_ci --exec $CRUISECONTROL_CMD -- start  >> /var/log/cruisecontrol/cruisecontrol.log 2>&1 &
-    echo "."
-    ;;
-  stop)
-    echo "Stopping CruiseControl"
-    PARPID=`cat $PIDFILE`
-    if [ "$PARPID" = "" ] ; then
-      echo "No pidfile found for cruisecontrol, nothing to stop"
-      exit 1
-    fi
-    start-stop-daemon --stop --quiet --pidfile $PIDFILE
-    echo "."
-    CHILDPIDS=`ps -ea -o "pid ppid args" | grep -v grep | grep "${PARPID}" | grep -v "^ ${PARPID}" | \
-      sed -e 's/^  *//' -e 's/ .*//'`
-    if [ "${CHILDPIDS}" != "" ]; then
-      echo "Killing child processes: $CHILDPIDS"
-      kill -9 ${CHILDPIDS}
-      echo "Done killing child processes."
-    else
-      echo "No child processes killed."
-    fi
-    ;;
-  restart)
-    $0 stop
-    sleep 2
-    $0 start
-    ;;
-  *)
-        echo "Usage: /etc/init.d/cruisecontrol {start|stop|restart}"
-        exit 1
-esac
-
-exit 0

data/lib/geminstaller/gem_command_line_proxy.rb

@@ -1,32 +0,0 @@
-module GemInstaller
-  class GemCommandLineProxy
-    GEM_ERROR_REGEXP = /^ERROR.*/
-    def run(args)
-      args_string = args.join(" ")
-      output = `gem #{args_string} 2>&1`
-      return_value = $?
-      lines = output.split("\n")
-      # return value is always zero on windows (from gem.bat), so we have to resort to parsing the output
-      error_in_output = false
-      lines.each do |line|
-        if line.match(GemInstaller::GemCommandLineProxy::GEM_ERROR_REGEXP)
-          error_in_output = true
-          break
-        end
-      end
-      if (return_value != 0 or error_in_output)
-        error_message = "Error: gem command failed.  Command was 'gem #{args_string}', return value was '#{return_value}'.  Output was:\n"
-        lines.each do |line| 
-          error_message += '  ' + line + '\n'
-        end
-        raise GemInstaller::GemInstallerError.new(error_message)
-      end
-      return lines
-    end
-  end
-end
-
-
-
-
-