rkh-bundler 1.2.0.pre

data/ISSUES.md

@@ -0,0 +1,67 @@
+# Bundler Issues
+
+## Troubleshooting
+
+Instructions for common Bundler use-cases can be found on the [Bundler documentation site](http://gembundler.com/v1.0/).
+
+Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://gembundler.com/man/bundle.1.html).
+
+After reading the documentation, try these troubleshooting steps:
+
+    # remove user-specific gems and git repos
+    rm -rf ~/.bundle/ ~/.gem/
+
+    # remove system-wide git repos and git checkouts
+    rm -rf $GEM_HOME/bundler/ $GEM_HOME/cache/bundler/
+
+    # remove project-specific settings and git repos
+    rm -rf .bundle/
+
+    # remove project-specific cached .gem files
+    rm -rf vendor/cache/
+
+    # remove the saved resolve of the Gemfile
+    rm -rf Gemfile.lock
+
+    # try to install one more time
+    bundle install
+
+## Frequently encountered issues
+
+### Heroku errors
+
+Open a ticket with Heroku. If the issue somehow turns out to be with Bundler itself, the Heroku support team will forward the details of your issue to us.
+
+### REE and Zlib::GzipFile::Error
+
+Ruby Enterprise Edition users may see a `Zlib::GzipFile::Error` while installing gems. It is due to [a bug in REE](http://code.google.com/p/rubyenterpriseedition/issues/detail?id=45). You may be able to resolve the issue by upgrading REE, or changing to a different interpreter.
+
+### Rake activation error
+
+Anyone who has installed the Spork gem may see activation errors while running `rake` directly. This is because old versions of Spork would [install the newest rake using a mkmf file](https://github.com/timcharper/spork/issues/119). To resolve the issue, update the Spork version requirement in your Gemfile to at least `"~>0.8.5"` or `"~>0.9.0.rc8"`.
+
+
+## Reporting unresolved problems
+
+Instructions that allow the Bundler team to reproduce your issue are vitally important. When you report a bug, please include the following information:
+
+  - The command you ran
+  - Exception backtrace(s), if any
+  - Your Gemfile
+  - Your Gemfile.lock
+  - Your Bundler configuration settings (run `bundle config`)
+  - What version of bundler you are using (run `bundle -v`)
+  - What version of Ruby you are using (run `ruby -v`)
+  - What version of Rubygems you are using (run `gem -v`)
+  - Whether you are using RVM, and if so what version (run `rvm -v`)
+  - Whether you have the `rubygems-bundler` gem, which can break gem binares
+  - Whether you have the `open_gem` gem, which can cause rake activation conflicts
+
+
+If you are using Rails 2.3, please also include:
+
+  - Your boot.rb file
+  - Your preinitializer.rb file
+  - Your environment.rb file
+
+[Create a gist](https://gist.github.com) containing all of that information, then visit the [Bundler issue tracker](https://github.com/carlhuda/bundler) and create a new ticket describing your problem and linking to your gist.

data/LICENSE

@@ -0,0 +1,23 @@
+Portions copyright (c) 2010 Andre Arko
+Portions copyright (c) 2009 Engine Yard
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,31 @@
+[![Build Status](https://secure.travis-ci.org/carlhuda/bundler.png?branch=master)](http://travis-ci.org/carlhuda/bundler)
+
+# Bundler: a gem to bundle gems
+
+Bundler is a tool that manages gem dependencies for your ruby application. It
+takes a gem manifest file and is able to fetch, download, and install the gems
+and all child dependencies specified in this manifest. It can manage any update
+to the gem manifest file and update the bundle's gems accordingly. It also lets
+you run any ruby code in context of the bundle's gem environment.
+
+### Installation and usage
+
+See [gembundler.com](http://gembundler.com) for up-to-date installation and usage instructions.
+
+### Troubleshooting
+
+For help with common problems, see [ISSUES](https://github.com/carlhuda/bundler/blob/master/ISSUES.md).
+
+### Development
+
+To see what has changed in recent versions of bundler, see the [CHANGELOG](https://github.com/carlhuda/bundler/blob/master/CHANGELOG.md).
+
+The `master` branch contains our current progress towards version 1.1. Because of that, please submit bugfix pull requests against the `1-0-stable` branch.
+
+### Upgrading from Bundler 0.8 to 0.9 and above
+
+See [UPGRADING](https://github.com/carlhuda/bundler/blob/master/UPGRADING.md).
+
+### Other questions
+
+Feel free to chat with the Bundler core team (and many other users) on IRC in the  [#bundler](irc://irc.freenode.net/bundler) channel on Freenode, or via email on the [Bundler mailing list](http://groups.google.com/group/ruby-bundler).

data/Rakefile

@@ -0,0 +1,208 @@
+# -*- encoding: utf-8 -*-
+$:.unshift File.expand_path("../lib", __FILE__)
+require 'rubygems'
+require 'bundler/gem_tasks'
+
+task :release => ["man:clean", "man:build"]
+
+def safe_task(&block)
+  yield
+  true
+rescue
+  false
+end
+
+def sudo_task(task)
+  system("sudo -E rake #{task}")
+end
+
+namespace :spec do
+  desc "Ensure spec dependencies are installed"
+  task :deps do
+    sh "#{Gem.ruby} -S gem list ronn | (grep 'ronn' 1> /dev/null) || #{Gem.ruby} -S gem install ronn --no-ri --no-rdoc"
+    sh "#{Gem.ruby} -S gem list rspec | (grep 'rspec (2.' 1> /dev/null) || #{Gem.ruby} -S gem install rspec --no-ri --no-rdoc"
+  end
+end
+
+begin
+  # running the specs needs both rspec and ronn
+  require 'rspec/core/rake_task'
+  require 'ronn'
+
+  desc "Run specs"
+  RSpec::Core::RakeTask.new do |t|
+    t.rspec_opts = %w(-fs --color)
+    t.ruby_opts  = %w(-w)
+  end
+  task :spec => "man:build"
+
+  namespace :spec do
+    task :clean do
+      rm_rf 'tmp'
+    end
+
+    desc "Run the real-world spec suite (requires internet)"
+    task :realworld => ["set_realworld", "spec"]
+
+    task :set_realworld do
+      ENV['BUNDLER_REALWORLD_TESTS'] = '1'
+    end
+
+    desc "Run the spec suite with the sudo tests"
+    task :sudo => ["set_sudo", "spec", "clean_sudo"]
+
+    task :set_sudo do
+      ENV['BUNDLER_SUDO_TESTS'] = '1'
+    end
+
+    task :clean_sudo do
+      puts "Cleaning up sudo test files..."
+      system "sudo rm -rf #{File.expand_path('../tmp/sudo_gem_home', __FILE__)}"
+    end
+
+    namespace :rubygems do
+      # Rubygems specs by version
+      rubyopt = ENV["RUBYOPT"]
+      %w(master v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.10).each do |rg|
+        desc "Run specs with Rubygems #{rg}"
+        RSpec::Core::RakeTask.new(rg) do |t|
+          t.rspec_opts = %w(-fs --color)
+          t.ruby_opts  = %w(-w)
+        end
+
+        # Create tasks like spec:rubygems:v1.8.3:sudo to run the sudo specs
+        namespace rg do
+          task :sudo => ["set_sudo", rg, "clean_sudo"]
+          task :realworld => ["set_realworld", rg]
+        end
+
+        task "clone_rubygems_#{rg}" do
+          unless File.directory?("tmp/rubygems")
+            system("git clone git://github.com/rubygems/rubygems.git tmp/rubygems")
+          end
+          hash = nil
+
+          Dir.chdir("tmp/rubygems") do
+            system("git remote update")
+            system("git checkout #{rg}")
+            system("git pull origin master") if rg == "master"
+            hash = `git rev-parse HEAD`.strip
+          end
+
+          puts "Running bundler specs against rubygems '#{rg}' at #{hash}"
+          ENV["RUBYOPT"] = "-I#{File.expand_path("tmp/rubygems/lib")} #{rubyopt}"
+        end
+
+        task rg => ["clone_rubygems_#{rg}", "man:build"]
+        task "rubygems:all" => rg
+      end
+
+      desc "Run specs under a Rubygems checkout (set RG=path)"
+      RSpec::Core::RakeTask.new("co") do |t|
+        t.rspec_opts = %w(-fs --color)
+        t.ruby_opts  = %w(-w)
+      end
+
+      task "setup_co" do
+        ENV["RUBYOPT"] = "-I#{File.expand_path ENV['RG']} #{rubyopt}"
+      end
+
+      task "co" => "setup_co"
+      task "rubygems:all" => "co"
+    end
+
+    desc "Run the tests on Travis CI against a rubygem version (using ENV['RGV'])"
+    task :travis do
+      rg = ENV['RGV'] || 'master'
+
+      puts "\n\e[1;33m[Travis CI] Running bundler specs against rubygems #{rg}\e[m\n\n"
+      specs = safe_task { Rake::Task["spec:rubygems:#{rg}"].invoke }
+
+      Rake::Task["spec:rubygems:#{rg}"].reenable
+
+      puts "\n\e[1;33m[Travis CI] Running bundler sudo specs against rubygems #{rg}\e[m\n\n"
+      sudos = sudo_task "spec:rubygems:#{rg}:sudo"
+      chown = system("sudo chown -R #{ENV['USER']} #{File.join(File.dirname(__FILE__), 'tmp')}")
+
+      Rake::Task["spec:rubygems:#{rg}"].reenable
+
+      puts "\n\e[1;33m[Travis CI] Running bundler real world specs against rubygems #{rg}\e[m\n\n"
+      realworld = safe_task { Rake::Task["spec:rubygems:#{rg}:realworld"].invoke }
+
+      unless specs && sudos && realworld
+        fail "Bundler tests failed, please review the log for more information"
+      end
+    end
+  end
+
+  namespace :man do
+    directory "lib/bundler/man"
+
+    Dir["man/*.ronn"].each do |ronn|
+      basename = File.basename(ronn, ".ronn")
+      roff = "lib/bundler/man/#{basename}"
+
+      file roff => ["lib/bundler/man", ronn] do
+        sh "#{Gem.ruby} -S ronn --roff --pipe #{ronn} > #{roff}"
+      end
+
+      file "#{roff}.txt" => roff do
+        sh "groff -Wall -mtty-char -mandoc -Tascii #{roff} | col -b > #{roff}.txt"
+      end
+
+      task :build_all_pages => "#{roff}.txt"
+    end
+
+    desc "Build the man pages"
+    task :build => "man:build_all_pages"
+
+    desc "Clean up from the built man pages"
+    task :clean do
+      rm_rf "lib/bundler/man"
+    end
+  end
+
+  begin
+    require 'ci/reporter/rake/rspec'
+
+    namespace :ci do
+      desc "Run specs with Hudson output"
+      RSpec::Core::RakeTask.new(:spec)
+      task :spec => ["ci:setup:rspec", "man:build"]
+    end
+
+  rescue LoadError
+    namespace :ci do
+      task :spec do
+        abort "Run `rake ci:deps` to be able to run the CI specs"
+      end
+
+      desc "Install CI dependencies"
+      task :deps do
+        sh "#{Gem.ruby} -S gem list ci_reporter | (grep 'ci_reporter' 1> /dev/null) || #{Gem.ruby} -S gem install ci_reporter --no-ri --no-rdoc"
+      end
+      task :deps => "spec:deps"
+    end
+  end
+
+rescue LoadError
+  task :spec do
+    abort "Run `rake spec:deps` to be able to run the specs"
+  end
+end
+
+namespace :vendor do
+  desc "Build the vendor dir"
+  task :build => :clean do
+    sh "git clone git://github.com/wycats/thor.git lib/bundler/vendor/tmp"
+    sh "mv lib/bundler/vendor/tmp/lib/* lib/bundler/vendor/"
+    rm_rf "lib/bundler/vendor/tmp"
+  end
+
+  desc "Clean the vendor dir"
+  task :clean do
+    rm_rf "lib/bundler/vendor"
+  end
+end
+
+task :default => :spec

data/UPGRADING.md

@@ -0,0 +1,103 @@
+## Bundler 0.9 to 1.0 and above
+
+Upgrading from Bundler 0.9 to 1.0 is relatively painless. The
+Gemfile API is the same, so your old Gemfiles should continue
+to work.
+
+The "env" file that 0.9 created at `.bundle/environment.rb` has been
+removed. As a side effect of this, Passenger will only find your
+bundled gems if you install with `bundle install --deployment`.
+Alternatively, you can tell Passenger where you gems are installed,
+[something like this](http://bit.ly/passenger-gem-home).
+
+The `bundle lock` command is no longer needed, as the
+Gemfile.lock file is now automatically generated by `bundle install`.
+If you have not yet done so, add your Gemfile.lock to source control
+and check it in.
+
+Running `bundle install` no longer updates the versions of your gems.
+If you need to update just one gem, run `bundle update GEMNAME`. To
+update all gems to the newest versions possible, run `bundle update`.
+
+Bundler now supports multiple platforms, using a block syntax to
+declare platform-specific gems:
+
+    platform :jruby do
+      gem "jruby-maven-plugins"
+    end
+
+Deploying using Bundler is even easier than it was before, as Bundler
+now includes a Capistrano recipe. Simply add this line to the top of
+your deploy.rb file to run Bundler automatically as part of deploying:
+
+    require 'bundler/capistrano'
+
+For more details on deploying using bundler, see the documentation
+for the bundler cap task, and the [documentation on deploying](http://gembundler.com/deploying.html).
+
+
+## Bundler 0.8 to 0.9 and above
+
+Upgrading to Bundler 0.9 from Bundler 0.8 requires upgrading several
+API calls in your Gemfile, and some workarounds if you are using Rails 2.3.
+
+### Gemfile Removals
+
+Bundler 0.9 removes the following Bundler 0.8 Gemfile APIs:
+
+1. `disable_system_gems`: This is now the default (and only) option
+   for bundler. Bundler uses the system gems you have specified
+   in the Gemfile, and only the system gems you have specified
+   (and their dependencies)
+2. `disable_rubygems`: This is no longer supported. We are looking
+   into ways to get the fastest performance out of each supported
+   scenario, and we will make speed the default where possible.
+3. `clear_sources`: Bundler now defaults to an empty source
+   list. If you want to include Rubygems, you can add the source
+   via source "http://gemcutter.org". If you use bundle init, this
+   source will be automatically added for you in the generated
+   Gemfile
+4. `bundle_path`: You can specify this setting when installing
+   via `bundle install /path/to/bundle`. Bundler will remember
+   where you installed the dependencies to on a particular
+   machine for future installs, loads, setups, etc.
+5. `bin_path`: Bundler no longer generates executables in the root
+   of your app. You should use `bundle exec` to execute executables
+   in the current context.
+
+### Gemfile Changes
+
+Bundler 0.9 changes the following Bundler 0.8 Gemfile APIs:
+
+1. Bundler 0.8 supported :only and :except as APIs for describing
+   groups of gems. Bundler 0.9 supports a single `group` method,
+   which you can use to group gems together. See the above "Group"
+   section for more information.
+
+   This means that `gem "foo", :only => :production` becomes
+   `gem "foo", :group => :production`, and
+   `only :production { gem "foo" }` becomes
+   `group :production { gem "foo" }`
+
+   The short version is: group your gems together logically, and
+   use the available commands to make use of the groups you've
+   created.
+
+2. `:require_as` becomes `:require`
+
+3. `:vendored_at` is fully removed; you should use `:path`
+
+### API Changes
+
+1. `Bundler.require_env(:environment)` becomes
+   `Bundler.require(:multiple, :groups)`. You must
+   now specify the default group (the default group is the
+   group made up of the gems not assigned to any group)
+   explicitly. So `Bundler.require_env(:test)` becomes
+   `Bundler.require(:default, :test)`
+
+2. `require 'vendor/gems/environment'`: In unlocked
+   mode, where using system gems, this becomes
+   `Bundler.setup(:multiple, :groups)`. If you don't
+   specify any groups, this puts all groups on the load
+   path. In locked mode, it becomes `require '.bundle/environment'`

data/bin/bundle

@@ -0,0 +1,31 @@
+#!/usr/bin/env ruby
+require 'bundler'
+begin
+  # Check if an older version of bundler is installed
+  $:.each do |path|
+    if path =~ %r'/bundler-0.(\d+)' && $1.to_i < 9
+      err = "Please remove Bundler 0.8 versions."
+      err << "This can be done by running `gem cleanup bundler`."
+      abort(err)
+    end
+  end
+  require 'bundler/cli'
+  Bundler::CLI.start
+rescue Bundler::BundlerError => e
+  Bundler.ui.error e.message
+  Bundler.ui.debug e.backtrace.join("\n")
+  exit e.status_code
+rescue Interrupt => e
+  Bundler.ui.error "\nQuitting..."
+  Bundler.ui.debug e.backtrace.join("\n")
+  exit 1
+rescue SystemExit => e
+  exit e.status
+rescue Exception => e
+  Bundler.ui.error "Unfortunately, a fatal error has occurred. " +
+    "Please report this error to the Bundler issue tracker at " +
+    "https://github.com/carlhuda/bundler/issues so that we can fix it. " +
+    "Please include the full output of the command, your Gemfile and Gemfile.lock. " +
+    "Thanks!"
+  raise e
+end