geminstaller 0.2.0 → 0.2.1

data/History.txt

@@ -1,4 +1,9 @@
+== 0.2.1 / 2007-06-07
+* Fixes to handle internal refactoring of command classes in RubyGems 0.9.3
+
+== 0.2.0 / 2007-05-13
+* First public release
+
 == 0.0.1 / 2006-07-29
 
-* 1 major enhancement
-  * Initial Creation
+* Initial Creation

data/Manifest.txt

@@ -11,6 +11,7 @@ lib/geminstaller.rb
 lib/geminstaller/application.rb
 lib/geminstaller/arg_parser.rb
 lib/geminstaller/autogem.rb
+lib/geminstaller/backward_compatibility.rb
 lib/geminstaller/config.rb
 lib/geminstaller/config_builder.rb
 lib/geminstaller/dependency_injector.rb
@@ -40,6 +41,7 @@ lib/geminstaller/rogue_gem_finder.rb
 lib/geminstaller/ruby_gem.rb
 lib/geminstaller/rubygems_exit.rb
 lib/geminstaller/rubygems_extensions.rb
+lib/geminstaller/rubygems_version_checker.rb
 lib/geminstaller/unauthorized_dependency_prompt_error.rb
 lib/geminstaller/unexpected_prompt_error.rb
 lib/geminstaller/valid_platform_selector.rb

data/TODO.txt

@@ -1,19 +1,29 @@
-* upload gem
-================ 0.2.0 release ===================
-* docs should indicate that I eat my own dog food
+* Fix broken doc links Jean-Michel reported
+* 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.
+* 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
+================ 0.2.5 release ===================
+* Rename API: autogem -> gem, run -> install
+================ 0.3.0 release =====================
 * update docs with details on how to handle unmet dependencies when -y is not specified
-* tutorial: rails
 * tutorial: using common or shared config files, with different configs for different environments - test (rspec) vs. dev (capistrano) vs. demo/staging/prod
 * tutorial: running via capistrano
 * crossreference front page, tutorials, and docs
 * put mongrel/rails startup bug in tracker, add link in "known bugs" section on home page.
 * links - rspec, rubygems
-================ 0.2.0 finishing website ===================
+* Set up cruise
+================ 0.3.1 finishing website ===================
 * make valid_platform_selector use data from tattle
 * autogem and run args can be passed as string or array
 * tell rspec not to alphabetize my specs, or figure out how to not run testgemhome in the middle and have it set up test gem home twice
 * better test coverage for --sudo and --exception options
-* Verify compatibility with RubyGems trunk - especially Gem::ListCommand vs. Gem::Commands::ListCommand
 * use rspec context_setup
 * split out geminstaller_spec into application_spec and geminstaller_spec.  Fix reference in docs / design
 * newlines printed between dots when "updating" message is included in error message
@@ -86,3 +96,4 @@
 * Add support, syntax, and options for uninstalling gems - completely, or down to highest specified version.
 * add feature to automatically warn if there is a more recent version of the gem available and check_for_upgrade == false.  Use "gem outdated" command
 * auto-generate geminstaller.yml files (possibly by parsing source, or based on all gems installed locally)
+================ 0.later.1 Unprioritized ===================

data/geminstaller.yml

@@ -2,6 +2,7 @@
 # GemInstaller config file which specifies the actual build, test, and doc dependencies for GemInstaller itself.
 defaults:
   install_options: --include-dependencies
+  fix_dependencies: true
 gems:
 - name: diff-lcs
   version: '>= 1.1.2'

data/lib/geminstaller/arg_parser.rb

@@ -9,7 +9,9 @@ module GemInstaller
     def parse(args = [])
       raise GemInstaller::GemInstallerError.new("Args must be passed as an array.") unless args.nil? or args.respond_to? :shift
       args = ARGV if args.nil? || args == []
+      # check to see if args is an array of (nothing but) gems here...  if so, set args as [@options[:gems] and return
 
+      raise GemInstaller::GemInstallerError.new("Error: An array of options to be populated must be injected prior to calling GemInstaller::ArgParser.parse") unless @options
       @options[:exceptions] = false
       @options[:redirect_stderr_to_stdout] = false
       @options[:silent] = false

data/lib/geminstaller/backward_compatibility.rb

@@ -0,0 +1,11 @@
+# this file supports backward compatibility for prior versions of RubyGems
+RUBYGEMS_VERSION_CHECKER = GemInstaller::RubyGemsVersionChecker.new
+
+# 0.9.3 reorganized commands to Gem::Commands:: module from Gem::
+if RUBYGEMS_VERSION_CHECKER.less_than?('0.9.3')
+  LIST_COMMAND_CLASS = Gem::ListCommand
+  QUERY_COMMAND_CLASS = Gem::QueryCommand
+else
+  LIST_COMMAND_CLASS = Gem::Commands::ListCommand
+  QUERY_COMMAND_CLASS = Gem::Commands::QueryCommand
+end

data/lib/geminstaller/dependency_injector.rb

@@ -126,4 +126,4 @@ module GemInstaller
       @app.output_filter = @output_filter
     end
   end
-end
+end

data/lib/geminstaller/exact_match_list_command.rb

@@ -1,5 +1,5 @@
 module GemInstaller
-  class ExactMatchListCommand < Gem::ListCommand
+  class ExactMatchListCommand < LIST_COMMAND_CLASS
     def execute
       string = get_one_optional_argument || ''
       # This overrides the default RubyGems ListCommand behavior of doing a wildcard match.  This caused problems
@@ -8,7 +8,7 @@ module GemInstaller
       options[:name] = /^#{string}$/i
       # Do a little metaprogramming magic to avoid calling the problematic execute method on the ListCommand
       # superclass, and instead directly call the method on the QueryCommand grandparent 'supersuperclass'
-      unbound_execute_method = Gem::QueryCommand.instance_method(:execute)
+      unbound_execute_method = QUERY_COMMAND_CLASS.instance_method(:execute)
       bound_execute_method = unbound_execute_method.bind(self)
       bound_execute_method.call
     end

data/lib/geminstaller/gem_runner_proxy.rb

@@ -11,7 +11,7 @@ module GemInstaller
       gem_runner.do_configuration(args)
       gem_cmd_manager = @gem_cmd_manager_class.instance
       gem_cmd_manager.ui = @enhanced_stream_ui
-      gem_cmd_manager.register_command @exact_match_list_command
+      gem_cmd_manager.commands[:list] = @exact_match_list_command
       
       exit_status = nil
       begin
@@ -27,8 +27,7 @@ module GemInstaller
     end
     
     def create_gem_runner
-      rubygems_version = Gem::RubyGemsVersion
-      if rubygems_version.index('0.8') == 0
+      if Gem::RubyGemsVersion.index('0.8') == 0
         @gem_runner_class.new()
       else
         @gem_runner_class.new(:command_manager => @gem_cmd_manager_class)

data/lib/geminstaller/requires.rb

@@ -1,15 +1,35 @@
 dir = File.dirname(__FILE__)
 
-# requires for rubygems
+
+# require for rubygems package
 require 'rubygems'
+
+# backward compability and version-checking stuff - must be required before it is used
+require 'rubygems/rubygems_version'
+require File.expand_path("#{dir}/rubygems_version_checker")
+
+# requires for rubygems internal classes
 require 'rubygems/doc_manager'
 require 'rubygems/config_file'
-require 'rubygems/cmd_manager'
+if RUBYGEMS_VERSION_CHECKER.less_than?('0.9.3')
+  require 'rubygems/cmd_manager'
+else
+  require 'rubygems/command_manager'
+end
 require 'rubygems/gem_runner'
 require 'rubygems/remote_installer'
 require 'rubygems/installer'
 require 'rubygems/validator'
 
+# these are order-dependent.  Any better way???
+unless RUBYGEMS_VERSION_CHECKER.less_than?('0.9.3')
+  require 'rubygems/commands/query_command'
+  require 'rubygems/commands/list_command'
+end
+
+# backward compability support for prior rubygems versions 
+require File.expand_path("#{dir}/backward_compatibility")
+
 # third party libs
 require 'erb'
 require 'optparse'

data/lib/geminstaller/rubygems_extensions.rb

@@ -2,4 +2,8 @@ module Gem
   class GemRunner
     public :do_configuration
   end
-end
+  class CommandManager
+    attr_reader :commands
+  end
+end
+

data/lib/geminstaller/rubygems_version_checker.rb

@@ -0,0 +1,9 @@
+module GemInstaller
+  class RubyGemsVersionChecker
+    def less_than?(compare_version, rubygems_version = Gem::RubyGemsVersion)
+      Gem::Version::Requirement.new(["< #{compare_version}"]).satisfied_by?(Gem::Version.new(rubygems_version))
+    end
+  end
+end
+
+RUBYGEMS_VERSION_CHECKER = GemInstaller::RubyGemsVersionChecker.new

data/lib/geminstaller.rb

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

data/website/src/code/index.page

@@ -6,7 +6,7 @@ h1. Design Notes
 These are some notes on the underlying design of GemInstaller, and the current state of development:
 
 * GemInstaller was developed from nothing but a concept, using "Behavior-Driven Development":http://behaviour-driven.org and "Rspec":http://rspec.rubyforge.org/.
-* GemInstaller uses "Dependency Injection", an architecture which has many benefits, including testability and enabling "loose coupling and high cohesion":http://www.c2.com/cgi/wiki?CouplingAndCohesion.  I originally started with "Needle":http://rubyforge.org/projects/needle/, a Ruby Dependency Injection framework, but switched to a simple home-grown approach in other to not have a dependency on the Needle gem.  Read more about Dependency Injection here:
+* GemInstaller uses "Dependency Injection", an architecture which has many benefits, including testability and enabling "loose coupling and high cohesion":http://www.c2.com/cgi/wiki?CouplingAndCohesion.  I originally started with "Needle":http://rubyforge.org/projects/needle/, a Ruby Dependency Injection framework, but switched to a simple home-grown approach in order to not have a dependency on the Needle gem.  Read more about Dependency Injection here:
 ** "http://onestepback.org/index.cgi/Tech/Ruby/DependencyInjectionInRuby.rdoc":http://onestepback.org/index.cgi/Tech/Ruby/DependencyInjectionInRuby.rdoc
 ** "http://onestepback.org/articles/depinj/":http://onestepback.org/articles/depinj/
 ** "http://martinfowler.com/bliki/InversionOfControl.html":http://martinfowler.com/bliki/InversionOfControl.html 

data/website/src/documentation/tutorials.page

@@ -74,21 +74,222 @@ 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
 
-TODO: Write this, for now see docs on "Using GemInstaller with Ruby on Rails or Other Ruby Apps":documentation.html#using_geminstaller_with_ruby_on_rails_or_other_ruby_apps. 
+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.
+
+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.
+
+Next, you need a *<code>geminstaller.yml</code>* config file.  Create this under the Rails <code>config</code> directory.  For details, see the documentation on the "config file":documentation.html#config_file and the tutorial on "bootstrapping your GemInstaller config with the <code>--print-rogue-gems</code> option":#bootstrapping_your_geminstaller_config.  Here's an example config which contains only entries for Mongrel and Rails, and ruby-doom:
+
+*RAILS_ROOT/config/geminstaller.yml*:
+<pre>
+\---
+defaults:
+  install_options: --include-dependencies
+gems:
+- name: ruby-doom
+  version: '= 0.8'
+- name: rails
+  version: '= 1.1.6'
+- name: mongrel
+  version: '= 1.0.1'
+  platform: <%= RUBY_PLATFORM =~ /mswin/ ? 'mswin32' : 'ruby'%>
+</pre>
+
+Once you have your *<code>geminstaller.yml</code>* created, the last step is to add calls to <code>GemInstaller.run</code> and <code>GemInstaller.autogem</code> in your boot.rb.  They should be placed right after the block which defines the RAILS_ROOT constant, as shown below ("..." indicates omitted lines):
+
+
+*RAILS_ROOT/config/boot.rb*:
+<pre>
+...
+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 (you can add any extra ones)
+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.run(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)
+...
+</pre>
+
+This example also has configurable variables which illustrate the common option arguments you can control.  The <code>--exceptions</code> argument will cause GemInstaller to raise an exception if errors occur, and thus abort Rails startup.  The <code>--sudo</code> argument causes GemInstaller to be run via sudo.
+
+Now, all you need to do is start Rails.  You can use Webrick with <code>ruby script/server</code>, or Mongrel with <code>mongrel_rails start</code>.  You should see the message from Geminstaller that the gems are being installed:
+
+<pre>
+$ ruby script/server
+GemInstaller is verifying gem installation: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+GemInstaller is automatically requiring gems: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+./script/../config/boot.rb:55:Warning: require_gem is obsolete.  Use gem instead.
+=> Booting WEBrick...
+GemInstaller is verifying gem installation: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+GemInstaller is automatically requiring gems: mongrel = 1.0.1, rails = 1.1.6, ruby-doom = 0.8
+=> Rails application started on http://0.0.0.0:3000
+=> Ctrl-C to shutdown server; call with --help for options
+[2007-05-13 22:41:37] INFO  WEBrick 1.3.1
+[2007-05-13 22:41:37] INFO  ruby 1.8.5 (2006-08-25) [i686-darwin8.7.1]
+[2007-05-13 22:41:37] INFO  WEBrick::HTTPServer#start: pid=2519 port=3000
+</pre>
+
+If that worked, good!  If not, carefully read the error message.  If it was a RubyGems failure (as opposed to a bug in GemInstaller), the "<code>gem</code>" command that GemInstaller tried to execute should be echoed as part of the error message.  Cut and paste this command onto the command line, and see if you get the same error.  If you do, then resolve it and the problem should go away under GemInstaller as well.
+
+For extra credit, we can write a simple Rails controller to verify that the correct gems are getting added to the load path by the <code>autogem</code> command.  First, create the Rails app and a controller:
+
+<pre>
+$ rails geminstaller_example
+$ ruby script/generate controller GemInstallerExample
+</pre>
+
+Next, create the Rails app.  You need...
+
+...an action:
+*RAILS_ROOT/app/controllers/gem_installer_example_controller.rb*
+<pre>
+class GemInstallerExampleController < ApplicationController
+  def index
+  end
+end
+</pre>
+
+...a sample rhtml page which will show your config and load path:
+*RAILS_ROOT/app/views/gem_installer/index.rhtml*
+<pre>
+<% config = File.open("#{RAILS_ROOT}/config/geminstaller.yml")
+   config_lines = config.read.gsub!("\n","<br/>") %>
+<hr/>
+<h2>geminstaller.yml</h2>
+<h2><%= config_lines %></h2>
+<hr/>
+<h2>Load Path: </h2>
+<h2><%= $:.join("\n") %></h2>
+<hr/>
+</pre>
+
+...a default route to your page:
+*RAILS_ROOT/config/routes.rb*
+<pre>
+...
+# Put the following line as the first route in the routes.rb file:
+map.connect '', :controller => "gem_installer_example"
+...
+</pre>
+
+...a GemInstaller config file:
+*RAILS_ROOT/config/geminstaller.yml*:
+<pre>
+\---
+defaults:
+  install_options: --include-dependencies
+gems:
+- name: ruby-doom
+  version: '= 0.8'
+</pre>
+
+...the modifications to boot.rb (comments and local variables omitted here for brevity):
+<pre>
+...
+unless defined?(RAILS_ROOT)
+...
+end
+
+############# Begin GemInstaller config - see http://geminstaller.rubyforge.org
+require "rubygems"
+require "geminstaller"
+config_paths = "#{File.expand_path(RAILS_ROOT)}/config/geminstaller.yml" 
+args = "--config #{config_paths}" 
+args += " --exceptions"
+args += " --sudo" unless RUBY_PLATFORM =~ /mswin/ 
+GemInstaller.run(args)
+GemInstaller.autogem(args)
+############# End GemInstaller config
+
+unless defined?(Rails::Initializer)
+...
+</pre>
+
+...and delete the public/index.html file:
+<pre>
+$ rm public/index.html
+</pre>
+
+Now, you should be able to start the example Rails app and navigate to <code>http://localhost:3000</code> to view your config file and load path with the gems auto-required:
+
+<pre>
+$ ... cd to root of your rails app ...
+$ mongrel_rails start
+</pre>
+
+...open http://localhost:3000, and you should see something like this:
+<pre>
+_____________________________
+geminstaller.yml
+/---
+defaults:
+install_options: --include-dependencies
+gems:
+- name: ruby-doom
+version: '= 0.8'
+_____________________________
+Load Path:
+...
+(lots of load path stuff omitted)
+...
+(here's our gem!)
+/usr/local/lib/ruby/gems/1.8/gems/ruby-doom-0.8/lib /usr/local/lib/ruby/gems/1.8/gems/sources-0.0.1/bin</pre>
+...
+(more stuff omitted)
+...
+</pre>
+
+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
 
-TODO: Write this, for now see docs on the "<code>--config</code>":documentation.html#config_option option. 
+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:
+
+* 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.
+
+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. 
 
 
 h2(#running_geminstaller_from_capistrano). Running GemInstaller from Capistrano
 
-TODO: Write this, for now see docs on  "Using GemInstaller from Other Ruby Apps":documentation.html#using_geminstaller_from_other_ruby_apps
+GemInstaller can be hooked in as a capistrano task.  This is a way to avoid having the boot.rb hacks run in demo or production, and possibly cause problems with app startup in these environments.  It also is a way to avoid the current bug with Rails and Mongrel gems not being loaded correctly if they are upgraded during the app startup process.
+
+TODO: Finish writing this, for now see docs on  "Using GemInstaller from Other Ruby Apps":documentation.html#using_geminstaller_from_other_ruby_apps
 
 See also: Docs on "Using GemInstaller from Other Ruby Apps":documentation.html#using_geminstaller_from_other_ruby_apps.
 

data/website/src/index.page

@@ -18,7 +18,7 @@ GemInstaller provides automated management of RubyGems.  It uses a simple YAML c
 
 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.x).
+It has been tested on all major platforms (mac, linux, windows), and recent versions of RubyGems (0.8.x through 0.9.4).
 
 h2. How do I get it?
 
@@ -32,7 +32,11 @@ h2. Who is responsible for GemInstaller?
 
 GemInstaller was created by "Chad Woolley":http://www.thewoolleyweb.com.
 
-h2. Known Bugs
+h2(#known_bugs). Known Bugs
 
 Currently (as of version 0.0.2), 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.  Researching and fixing this problem is a top priority.  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.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

@@ -1,10 +1,10 @@
 --- !ruby/object:Gem::Specification 
-rubygems_version: 0.9.2
+rubygems_version: 0.9.4
 specification_version: 1
 name: geminstaller
 version: !ruby/object:Gem::Version 
-  version: 0.2.0
-date: 2007-05-13 00:00:00 -07:00
+  version: 0.2.1
+date: 2007-06-07 00:00:00 -07:00
 summary: GemInstaller provides automated management of RubyGems.
 require_paths: 
 - lib
@@ -42,6 +42,7 @@ files:
 - lib/geminstaller/application.rb
 - lib/geminstaller/arg_parser.rb
 - lib/geminstaller/autogem.rb
+- lib/geminstaller/backward_compatibility.rb
 - lib/geminstaller/config.rb
 - lib/geminstaller/config_builder.rb
 - lib/geminstaller/dependency_injector.rb
@@ -71,6 +72,7 @@ files:
 - lib/geminstaller/ruby_gem.rb
 - lib/geminstaller/rubygems_exit.rb
 - lib/geminstaller/rubygems_extensions.rb
+- lib/geminstaller/rubygems_version_checker.rb
 - lib/geminstaller/unauthorized_dependency_prompt_error.rb
 - lib/geminstaller/unexpected_prompt_error.rb
 - lib/geminstaller/valid_platform_selector.rb
@@ -93,10 +95,14 @@ files:
 - website/src/index.page
 test_files: 
 - test/test_all.rb
-rdoc_options: []
-
-extra_rdoc_files: []
-
+rdoc_options: 
+- --main
+- README.txt
+extra_rdoc_files: 
+- History.txt
+- Manifest.txt
+- README.txt
+- TODO.txt
 executables: 
 - geminstaller
 extensions: []