geminstaller 0.4.1 → 0.4.2

data/History.txt

@@ -1,3 +1,6 @@
+== 0.4.2 / 2008-06-19
+* Compatibility with RubyGems 1.2.0
+
 == 0.4.1 / 2008-04-12
 * Fix bug with warnings for outdated/incompatible rubygems versions.
 

data/README.txt

@@ -3,26 +3,27 @@ GemInstaller
     http://geminstaller.rubyforge.org
 
 == DESCRIPTION:
-  
-GemInstaller provides automated management of RubyGems.
+
+Automated Gem installation, activation, and much more!
 
 == FEATURES:
   
-GemInstaller provides automated management of RubyGems.  It uses a simple YAML config file to:
+GemInstaller provides automated installation, loading and activation 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 activate correct versions of gems on 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
+* Solve world hunger, prevent the global energy crisis, and wash your socks.
 
 == SYNOPSYS:
 
-GemInstaller provides automated management of RubyGems.
+Automated Gem installation, activation, and much more!
 
 === Download:
 

data/Rakefile

@@ -46,6 +46,13 @@ task :coverage do
   sh "rcov -o website/output/code/coverage test/test_all.rb"
 end
 
+task :coverage_no_fail do
+  begin
+    Rake::Task[:coverage].invoke
+  rescue
+  end
+end
+
 desc "Diff the manifest"
 task :diff_manifest => :clean do
   f = "Manifest.tmp"
@@ -91,7 +98,15 @@ task :website => [:webgen, :website_rdocs, :coverage] do
 end
 
 desc 'Publish website to RubyForge'
-task :publish_website => [:clean, :website] do
+task :publish_website => [:clean, :website, :upload_website] do
+end
+
+desc 'Publish website to RubyForge even if test coverage run rails'
+task :publish_website_no_fail => [:clean, :webgen, :website_rdocs, :coverage_no_fail, :upload_website] do
+end
+
+desc 'Upload website (should already be clean and generated)'
+task :upload_website do
   host = "thewoolleyman@rubyforge.org"
   remote_dir = "/var/www/gforge-projects/geminstaller"
   local_dir = 'website/output'

data/TODO.txt

@@ -1,15 +1,29 @@
 =============== Unfiled =============
+* Tagline: "It's not just for installing gems!" - "removes the drudgery of installing, activating, and requiring gems"
+* move to Github
+  * autoupdate of rails trunk
+  * redirection of links to old svn
+* Rename autogem to activate
+* add GemInstaller.require
+* Replace Tagline / Summary / Readme with "Install, Activate, and Require"
+* Big Quick Start Link on homepage
+* Update config.gems faq item with link to rails tutorial
+* rename sample app to rails_fixture_app, update important files with comments pointing to fixture app
+* examples dir
+  * geminstaller_merb_example_app
+  * geminstaller_rails_example_app
+* Update Rails tutorial link with link to example app
 ================ 0.4.0 release ===================
 * fix smoke tests on CI
 * Investigate error when installing and loading gem in same session (like rails preinitializer) - Not reproducible - fixed in >1.1.0???
 ================ 0.5.0 release ===================
-* If permission error, auto-install under writable_gem_home ~/gems/1.8 (configurable), Gem.clear_paths, set ENV['GEM_HOME'] to ENV['HOME']pathsepGem::ConfigMap[:ruby_version], and issue warning (saying in order to prevent warning, a) set gem_home: in ~/.gemrc, b) invoke via sudo (only if command line), c) make (and keep) current Gem.dir writeable, or d) add geminstaller (and ruby?) to sudoers file (security hole).  Properties: "[no_]use_writable_gem_home" and "writable_gem_home".
+* If permission error, auto-install under writable_gem_home ~/gems/1.8 (configurable), Gem.clear_paths, set ENV['GEM_HOME'] and ENV['GEM_PATH'] to ENV['HOME']pathsepGem::ConfigMap[:ruby_version], and issue warning (saying in order to prevent warning, a) set gem_home and gem_path: in ~/.gemrc, b) invoke via sudo (only if command line), c) make (and keep) current Gem.dir writeable, or d) add geminstaller (and ruby?) to sudoers file (security hole).  Properties: "[no_]use_writable_gem_home" and "writable_gem_home".
 * For RubyGems >=1.0.1, look at using Gem::SourceInfoCache instead of SourceIndex or --list command
 * Move classes which are unused against current RubyGems into Legacy module.
 * Speed! What can be done to speed things up?
 * performance improvement: first try cache hit without all option, then with if not found.
 * add command line tool to automatically generate files - default file, rake task (geminstaller:run, geminstaller:install, geminstaller:autogem), and preinit hook.  Auto-detect rails vs. non-rails project and generate stuff accordingly.  --setup, --setup-rails.  Check for new-style boot.rb, fail if missing, check for RAILS_GEM_VERSION in environment.rb, warn if present.
-* Merb support.  Does merb have preinitializer.rb equivalent?
+* Merb support.  init.rb.  See lightning talk.
 * Change 'run' to automatically automatically calls both 'install' and 'autogem', add 'no-install' and 'no-autogem' option (only applicable when invoked programatically) to suppress if desired
 * auto-install on app startup should not be the default unless use_writable_gem_home is implemented, because of sudo/rake doublerun/speed issues.  Update autogem missing gem error message accordingly.
 * also look for config file under RAILS_ROOT/config, if RAILS_ROOT is defined (somehow fails under textmate, if working dir is wrong)
@@ -20,7 +34,7 @@
 * add auto-install option if gem version error is detected, update error message saying to set option
 * cryptic message if "name:" is left off in yaml
 * Add option to auto-update rubygems to specified version.  See rubygems mailing list thread for details
-* set up sample rails project with geminstaller hook and sample test under CI.  Have cruise_config uninstall a dummy gem before rails tests, then have rails test ensure it was installed and loaded.
+* set up sample rails project with geminstaller hook and sample test under CI.  Have cruise_config uninstall a dummy gem before rails tests, then have rails test ensure it was installed and loaded. (done but not running under CI yet)
 ================ 0.x.x release ===================
 * turn smoketest into rake task, with correct return code handling, and hook up to cruise
 * look into and explain mongrel/webrick installation errors

data/geminstaller.yml

@@ -8,6 +8,8 @@ gems:
   version: '>= 1.1.2'
 - name: hoe
   version: '>= 1.4.0'
+- name: open4
+  version: '>= 0.9.6'
 - name: rake
   version: '>= 0.7.1'
 - name: rcov

data/lib/geminstaller/gem_command_manager.rb

@@ -31,9 +31,12 @@ module GemInstaller
       # with enhanced_stream_ui.  Patched: http://rubyforge.org/tracker/index.php?func=detail&aid=9020&group_id=126&atid=577
       # TODO: use pipe option on later versions which support it
       
-      run_args = ["dependency","^#{name}$","--version",version]
+      name_regexp = "^#{name}$"
+      name_regexp = "/#{name_regexp}/" if GemInstaller::RubyGemsVersionChecker.matches?('>=1.2.0')
+      run_args = ["dependency", name_regexp, "--version", version]
       run_args += additional_options
       output_lines = @gem_runner_proxy.run(run_args)
+      p output_lines
       # dependency output has all lines in the first element
       output_array = output_lines[0].split("\n")
       # drop the first line which just echoes the dependent gem
@@ -49,7 +52,7 @@ module GemInstaller
       # convert into gems
       output_gems = output_array.collect do |line|
         name = line.split(' ')[0]
-        version_spec = line.split(/[()]/)[1]
+        version_spec = line.split(/[(,)]/)[1]
         GemInstaller::RubyGem.new(name, :version => version_spec)
       end
     end

data/lib/geminstaller/registry.rb

@@ -38,7 +38,7 @@ module GemInstaller
       @config_builder.yaml_loader = @yaml_loader
       @config_builder.output_filter = @output_filter
 
-      @gem_source_index = Gem::SourceIndex.new
+      @gem_source_index = Gem::SourceIndex.from_installed_gems
       @gem_source_index_proxy = GemInstaller::GemSourceIndexProxy.new
       @gem_source_index_proxy.gem_source_index = @gem_source_index
 

data/lib/geminstaller.rb

@@ -34,7 +34,7 @@ module GemInstaller
   end
 
   def self.version
-    "0.4.1"
+    "0.4.2"
   end
 
   def self.create_application(args = [], registry = nil)

data/website/src/code/index.page

@@ -32,7 +32,7 @@ These are some notes on the underlying design of GemInstaller, and the current s
 <span id="rubygems_compatibility"/>
 h1. Maintaining forward and backward compatibility with multiple RubyGems versions
 
-* I've put a lot of effort into ensuring that GemInstaller works with older versions of RubyGems.  As of now (2008-01-01) all specs (not smoketests) are green on mac/linux against RubyGems versions 0.8.11, 0.9.4, 0.9.5, 1.0.0, and 1.0.1.  On Windows, smoketests and specs are green against 1.0.1.  I haven't figured out how to automate testing against older RubyGems versions without a reinstall on Windows, so let me know if something is broken (or just upgrade).
+* I've put a lot of effort into ensuring that GemInstaller works with older versions of RubyGems, and run automated tests against several recent versions on Continuous Integration.
 
 * This wasn't as hard as it seems.  The hardest part was figuring out what was different between versions.  Once you understand that, you can add switch statements to perform different logic or tests depending on the version (which is easy if you use rubygems built in Version Requirement support - see GemInstaller::RubygemsVersionChecker).
 

data/website/src/community/index.page

@@ -6,7 +6,7 @@ h1. Feedback, Bugs, and Source Code
 h2. Rubyforge Bug/Feature Tracker and Mailing Lists
 
 * "RubyForge Page":http://rubyforge.org/projects/geminstaller/
-* "Bug/Feature Tracker":http://rubyforge.org/tracker/?group_id=1902
+* "Bug/Feature Tracker":http://thewoolleyweb.lighthouseapp.com/projects/11580-geminstaller/overview
 * "Mailing Lists":http://rubyforge.org/mail/?group_id=1902
 
 h2. Source Code

data/website/src/default.template

@@ -19,7 +19,7 @@
       <div id="header">
         <div id="sitename">
           <h1>GemInstaller</h1>
-          <h2>Automate Ruby Gems!</h2>
+          <h2>Automated Gem installation, activation, and much more!</h2>
         </div>
       </div>
 

data/website/src/documentation/documentation.page

@@ -377,6 +377,12 @@ 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>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.
+
+<strong>FOR NOW, THOUGH:</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.
 
 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.

data/website/src/documentation/index.page

@@ -21,6 +21,12 @@ gems:
 
 h2. Using GemInstaller with Ruby on Rails
 
+<strong>RAILS 2.0 UPDATE:</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/
+
+<strong>OLD RAILS 1.0 INSTRUCTIONS:</strong>
+
 * 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>

data/website/src/documentation/tutorials.page

@@ -74,9 +74,13 @@ See also:  Docs on "Automatically Requiring Gems with the <code>autogem</code> M
 
 h2(#integrating_geminstaller_into_ruby_on_rails). Integrating GemInstaller into Ruby on Rails
 
-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.
+<strong>RAILS 2.0 UPDATE:</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/
 
-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.
+<strong>OLD RAILS 1.0 INSTRUCTIONS:</strong>
+
+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.
 
 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.
 

data/website/src/faq.page

@@ -3,10 +3,13 @@ title: FAQ
 ---
 h1. Frequently Asked Questions
 
+<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 :)
 
 <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.
+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!  The workaround would be to not use sudo (http://thewoolleyweb.lighthouseapp.com/projects/11580/tickets/1-automatically-create-use-and-manage-writeable-gem-home-if-system-gem-home-is-not-writeable)
 
 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.
@@ -17,6 +20,9 @@ A: You are on your own, this is outside of the scope of GemInstaller.  The gemin
 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.
 
+Q: Why else should I support GemInstaller?<br/>
+A: GemInstaller has an extensive, multifaceted and multiplatform suite of specs and tests which is actively maintained against the latest trunk version of RubyGems and run via Continuous Integration.  It is valuable for alerting about regressions in RubyGems itself.  For example, leading up to the the RubyGems 1.2.0 release, the GemInstaller spec suite identified several regression bugs in RubyGems which were promptly reported and proactively fixed by awesome Eric Hodel and others before the release.
+
 
 <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

@@ -5,17 +5,18 @@ h1. Overview
 
 h2. What is GemInstaller?
 
-GemInstaller provides automated management of RubyGems.  It uses a simple YAML config file to:
+GemInstaller provides automated installation, loading and activation 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 activate correct versions of gems on 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
+* Avoid the "works on demo, breaks on production" syndrome.
+* Solve world hunger, prevent the global energy crisis, and wash your socks.
 
 GemInstaller can be used from the command line, or embedded to run automatically on startup for a Rails app or any other Ruby program.
 
@@ -33,16 +34,24 @@ h2. Who is responsible for GemInstaller?
 
 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.
+
 h2(#news). News
 
-Version 0.4.0 of GemInstaller is released.  This is tested and working against RubyGems 1.1.1.  Version 1.1.0 of RubyGems had some problems with GemInstaller, and is not supported.
+Version 0.4.1 of GemInstaller is released.  This is tested and working against RubyGems 1.1.1.  Version 1.1.0 of RubyGems had some problems with GemInstaller, and is not supported.
 
 h2(#known_issues). Known Issues
 
-Please "report them if you find them":http://rubyforge.org/tracker/?group_id=1902!
+I have a "list of high priority bugs and features":http://thewoolleyweb.lighthouseapp.com/projects/11580-geminstaller/tickets?q=tagged%3Ahigh_priority that need to be addressed before a 1.0 release.
+
+Please "report any others that you find":http://thewoolleyweb.lighthouseapp.com/projects/11580-geminstaller/overview !
 
 h2(#history). History
 
+* 0.4.2
+** Compatibility with RubyGems 1.2.0
 * 0.4.1
 ** Fix bug with warnings for outdated/incompatible rubygems versions.
 * 0.4.0

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: geminstaller
 version: !ruby/object:Gem::Version 
-  version: 0.4.1
+  version: 0.4.2
 platform: ruby
 authors: 
 - Chad Woolley
@@ -9,11 +9,11 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2008-04-12 00:00:00 -07:00
+date: 2008-06-24 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."
+description: "Automated Gem installation, activation, and much more!  == FEATURES:  GemInstaller provides automated installation, loading and activation 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 activate correct versions of gems on 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 * Solve world hunger, prevent the global energy crisis, and wash your socks.  == SYNOPSYS:"
 email: thewoolleyman@gmail.com
 executables: 
 - geminstaller
@@ -124,9 +124,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: geminstaller
-rubygems_version: 1.1.1
+rubygems_version: 1.2.0
 signing_key: 
 specification_version: 2
-summary: GemInstaller provides automated management of RubyGems.
+summary: Automated Gem installation, activation, and much more!
 test_files: 
 - test/test_all.rb