bundler 1.9.0 → 1.17.3

data/.gitignore

@@ -1,16 +0,0 @@
-# Please do not submit patches for including directives to ignore IDE/editor
-# generated files. Use a global gitignore as described in
-# https://help.github.com/articles/ignoring-files and find useful gitignore
-# samples at https://github.com/github/gitignore
-
-# files created by running the specs
-/tmp/
-
-# gems built by `rake build`
-/pkg/
-
-# output from ronn
-/lib/bundler/man/
-
-# output from ci_reporter
-/spec/reports/

data/.rspec

@@ -1,3 +0,0 @@
---format documentation
---color
---warnings

data/.travis.yml

@@ -1,110 +0,0 @@
-language: ruby
-script: rake spec:travis
-before_script: travis_retry rake spec:travis:deps
-
-branches:
-  only:
-    - master
-    - 1-8-stable
-    - 1-7-stable
-    - 1-6-stable
-    - 1-5-stable
-    - 1-3-stable
-    - 1-2-stable
-    - 1-1-stable
-    - 1-0-stable
-
-notifications:
-  email:
-    # andre
-    - secure: "bCcvqJT7YrBawtkXXwHhT+jOFth7r2Qv/30PkkbhQxk6Jb3xambjCOJ3U6vJ\ngYmiL50exi5lUp3oc3SEbHN5t2CrZqOZDQ6o7P8EAmB5c0oH2RrYaFOkI5Gt\nul/jGH/96A9sj0aMwG7JfdMSfhqj1DUKAm2PnnbXPL853VfmT24="
-    # terence
-    - secure: "MQ8eA5Jb8YzEpAo58DRGfVJklAPcEbAulpBZnTxp0am6ldneDtJHbQk21w6R\nj5GsDHlzr/lMp/GHIimtUZ7rLohfND8fj/W7fs1Dkd4eN02/ERt98x3pHlqv\nvZgSnZ39uVYv+OcphraE24QaRaGWLhWZAMYQTVe/Yz50NyG8g1U="
-  slack:
-    on_success: change
-    on_failure: always
-    rooms:
-      - secure: JxBi7DDJGkIF/7f/FSN/HUHpvV4EKfQccZHTPd1b2pNJn3GXo6u+tNVbAw2WjxYzPyPQI3ZcYBCU9SEXp/i7VmG8uMzh8Kyildw+miSKYKVb90uYqcsXWzbxwyNBgJLvyDkzST45H5lgnyAicee3WkFes/WDZikIajbH7ztdb04=
-
-rvm:
-  - 2.2
-  - 2.1
-  - 2.0.0
-  - 1.9.3
-  - 1.8.7
-
-# Rubygems versions MUST be available as rake tasks
-# see Rakefile:66 for the list of possible RGV values
-env:
-  # We need to know if changes to rubygems will break bundler on release
-  - RGV=master
-  # Test the latest rubygems release with all of our supported rubies
-  - RGV=v2.4.6
-
-matrix:
-  fast_finish: true
-  include:
-    # Ruby 2.2, Rubygems 2.4.5 and up (RG 2.4 is included by the matrix above)
-    # Ruby 2.1, Rubygems 2.2.2 and up
-    - rvm: 2.1
-      env: RGV=v2.2.3
-    # Ruby 2.0.0, Rubygems 2.0.0 and up
-    - rvm: 2.0.0
-      env: RGV=v2.2.3
-    - rvm: 2.0.0
-      env: RGV=v2.1.11
-    - rvm: 2.0.0
-      env: RGV=v2.0.14
-    # Ruby 1.9.3, Rubygems 1.5.3 and up
-    - rvm: 1.9.3
-      env: RGV=v2.2.3
-    - rvm: 1.9.3
-      env: RGV=v2.1.11
-    - rvm: 1.9.3
-      env: RGV=v2.0.14
-    - rvm: 1.9.3
-      env: RGV=v1.8.29
-    - rvm: 1.9.3
-      env: RGV=v1.7.2
-    - rvm: 1.9.3
-      env: RGV=v1.6.2
-    - rvm: 1.9.3
-      env: RGV=v1.5.3
-    # Ruby 1.8.7, Rubygems 1.3.6 and up
-    - rvm: 1.8.7
-      env: RGV=v2.2.3
-    - rvm: 1.8.7
-      env: RGV=v2.0.14
-    - rvm: 1.8.7
-      env: RGV=v1.8.29
-    - rvm: 1.8.7
-      env: RGV=v1.7.2
-    - rvm: 1.8.7
-      env: RGV=v1.6.2
-    - rvm: 1.8.7
-      env: RGV=v1.5.3
-    - rvm: 1.8.7
-      env: RGV=v1.4.2
-    - rvm: 1.8.7
-      env: RGV=v1.3.7
-    - rvm: 1.8.7
-      env: RGV=v1.3.6
-
-    # ALLOWED FAILURES
-    # For no apparent reason, this often goes over the Travis limit
-    - rvm: 1.8.7
-      env: RGV=v2.1.11
-    # Ruby 1.9.2 sanity check
-    # (but it's just too slow and sometimes goes over the Travis limit)
-    - rvm: 1.9.2
-      env: RGV=v2.4.6
-    # Ruby-head (we want to know how we're doing, but not fail the build)
-    - rvm: ruby-head
-      env: RGV=master
-  allow_failures:
-    - rvm: 1.8.7
-      env: RGV=v2.1.11
-    - rvm: 1.9.2
-    - rvm: ruby-head
-    - rvm: jruby
-    - rvm: rbx-2

data/CODE_OF_CONDUCT.md

@@ -1,40 +0,0 @@
-# Bundler Code of Conduct
-
-The Bundler project strongly values contributors from anywhere, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. As a result, the Bundler team has agreed to and enforces this code of conduct in order to provide a harassment-free experience for everyone who participates in the development of Bundler.
-
-### Summary
-
-Harassment in code and discussion or violation of physical boundaries is completely unacceptable anywhere in the Bundler project’s codebases, issue trackers, IRC channel, Campfire, mailing lists, meetups, and other events. Violators will be warned and then blocked or banned by the core team at or before the 3rd violation.
-
-### In detail
-
-Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images, deliberate intimidation, stalking, sustained disruption, and unwelcome sexual attention.
-
-Individuals asked to stop any harassing behavior are expected to comply immediately.
-
-Maintainers, including the core team, are also subject to the anti-harassment policy.
-
-If anyone engages in harassing behavior, including maintainers, we may take appropriate action, up to and including warning the offender, deletion of comments, removal from the project’s codebase and communication systems, and escalation to Github support.
-
-If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of [the core team](http://bundler.io/contributors.html) or [email the core team](mailto:team@bundler.io) immediately.
-
-We expect everyone to follow these rules anywhere in the Bundler project’s codebases, issue trackers, IRC channel, group chat, and mailing lists.
-
-Finally, don't forget that it is human to make mistakes! We all do. Let’s work together to help each other, resolve issues, and learn from the mistakes that we will all inevitably make from time to time.
-
-
-### Thanks
-
-Thanks to the [JSConf Code of Conduct](http://jsconf.com/codeofconduct.html) and [Fedora Code of Conduct](http://fedoraproject.org/code-of-conduct) for inspiration and ideas. Additional thanks to [Contributor Covenant](http://contributor-covenant.org) for the [default code of conduct](https://github.com/bundler/bundler/blob/master/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt) included in generated gems.
-
-
-### License
-
-<p class="license" xmlns:dct="http://purl.org/dc/terms/" xmlns:vcard="http://www.w3.org/2001/vcard-rdf/3.0#">
-  To the extent possible under law, <a rel="dct:publisher" href="http://bundler.io">The Bundler Team</a> has waived all copyright and related or neighboring rights to the <span property="dct:title">Bundler Code of Conduct</span>. This work is published from the <span property="vcard:Country" datatype="dct:ISO3166" content="US" about="http://bundler.io">United States.</span>
-  <br>
-  <br>
-  <a rel="license" href="http://creativecommons.org/publicdomain/zero/1.0/">
-    <img src="http://i.creativecommons.org/p/zero/1.0/88x31.png" style="border-style: none;" alt="CC0">
-  </a>
-</p>

data/CONTRIBUTING.md

@@ -1,32 +0,0 @@
-# Contributing
-
-Bundler welcomes contributions from *everyone*. While contributing, please follow the project [code of conduct](http://bundler.io/conduct.html), so that everyone can be included.
-
-If you'd like to help make Bundler better, you totally rock! Here are some ways you can contribute:
-
-  - by using prerelease versions (run `gem install bundler --pre`)
-  - by [reporting bugs you encounter](https://github.com/bundler/bundler/issues/new)
-  - by [suggesting new features](https://github.com/bundler/bundler-features/issues/new)
-  - by adding to or editing [the Bundler documentation website](http://bundler.io) and [Bundler man pages](http://bundler.io/man/bundle.1.html)
-  - by [checking issues for completeness](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md#bug-triage)
-  - by closing issues that are not complete
-  - by adding a failing test for reproducible [reported bugs](https://github.com/bundler/bundler/issues)
-  - by reviewing [pull requests](https://github.com/bundler/bundler/pulls) and suggesting improvements
-  - by improving existing code, including [suggestions from PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master)
-  - by [writing code](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) (no patch is too small! fix typos or bad whitespace)
-
-If you need help getting started, check out the [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) file for steps that will get you up and running.
-
-Thanks for helping us make Bundler better.
-
-# Troubleshooting
-
-If you're having a problem, please see [ISSUES](https://github.com/bundler/bundler/blob/master/ISSUES.md) for troubleshooting steps and a guide for how to submit a ticket that will help us solve the problem you are having as quickly as possible.
-
-# Requesting Features
-
-Head on over to the [Bundler features](https://github.com/bundler/bundler-features) project, or any of the lists or channels listed below. Feature-wise we consider Bundler stable, so the core team does not tend to work on feature suggestions. Pull requests welcome though!
-
-# Discussing Bundler
-
-If you'd like to discuss features, ask questions, or just engage in general Bundler-focused discussion, please see the [#bundler](irc://irc.freenode.net/#bundler) IRC channel on Freenode, and the [Bundler mailing list](http://groups.google.com/group/ruby-bundler) on Google Groups.

data/DEVELOPMENT.md

@@ -1,119 +0,0 @@
-Great to have you here! Here are a few ways you can help out with [Bundler](http://github.com/bundler/bundler).
-
-# Where should I start?
-
-You can start learning about Bundler by reading [the documentation](http://bundler.io). If you want, you can also read a (lengthy) explanation of [why Bundler exists and what it does](http://bundler.io/rationale.html). You can also check out discussions about Bundler on the [Bundler mailing list](https://groups.google.com/group/ruby-bundler) and in the [Bundler IRC channel](http://webchat.freenode.net/?channels=%23bundler), which is #bundler on Freenode. Please note that this project is released with a contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.
-
-## Your first commits
-
-If you’re interested in contributing to Bundler, that’s awesome! We’d love your help.
-
-If you have any questions after reading this page, please feel free to contact either [@indirect](http://github.com/indirect) or [@hone](http://github.com/hone). They are both happy to provide help working through your first bugfix or thinking through the problem you’re trying to resolve.
-
-## Tackle some small problems
-
-We track [small
-bugs](https://github.com/bundler/bundler/issues?labels=small&state=open) and [small features](https://github.com/bundler/bundler-features/issues?labels=small&state=open) so that anyone who wants to help can start with something that's not too overwhelming. If nothing on those lists looks good, though, just talk to us.
-
-
-# Development setup
-
-Bundler doesn't use a Gemfile to list development dependencies, because when we tried it we couldn't tell if we were awake or it was just another level of dreams. To work on Bundler, you'll probably want to do a couple of things.
-
-  1. Install Bundler's development dependencies
-
-        $ rake spec:deps
-
-  2. Run the test suite, to make sure things are working
-
-        $ rake spec
-
-  3. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
-
-        $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/bin/bundle'
-
-     With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command.
-
-
-# Bug triage
-
-Triage is the work of processing tickets that have been opened into actionable issues, feature requests, or bug reports. That includes verifying bugs, categorizing the ticket, and ensuring there's enough information to reproduce the bug for anyone who wants to try to fix it.
-
-We've created an [issues guide](https://github.com/bundler/bundler/blob/master/ISSUES.md) to walk Bundler users through the process of troubleshooting issues and reporting bugs.
-
-If you'd like to help, awesome! You can [report a new bug](https://github.com/bundler/bundler/issues/new) or browse our [existing open tickets](https://github.com/bundler/bundler/issues).
-
-Not every ticket will point to a bug in Bundler's code, but open tickets usually mean that there is something we could improve to help that user. Sometimes that means writing additional documentation, sometimes that means making error messages clearer, and sometimes that means explaining to a user that they need to install git to use git gems.
-
-When you're looking at a ticket, here are the main questions to ask:
-
-  * Can I reproduce this bug myself?
-  * Are the steps to reproduce clearly stated in the ticket?
-  * Which versions of Bundler (1.1.x, 1.2.x, git, etc.) manifest this bug?
-  * Which operating systems (OS X, Windows, Ubuntu, CentOS, etc.) manifest this bug?
-  * Which rubies (MRI, JRuby, Rubinius, etc.) and which versions (1.8.7, 1.9.3, etc.) have this bug?
-
-If you can't reproduce an issue, chances are good that the bug has been fixed (hurrah!). That's a good time to post to the ticket explaining what you did and how it worked.
-
-If you can reproduce an issue, you're well on your way to fixing it. :) Fixing issues is similar to adding new features:
-
-  1. Discuss the fix on the existing issue. Coordinating with everyone else saves duplicate work and serves as a great way to get suggestions and ideas if you need any.
-  2. Base your commits on the correct branch. Bugfixes for 1.x versions of Bundler should be based on the matching 1-x-stable branch.
-  3. Commit the code and at least one test covering your changes to a named branch in your fork.
-  4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the “Bugfixes” heading.
-  5. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your bugfix branch.
-
-Finally, the ticket may be a duplicate of another older ticket. If you notice a ticket is a duplicate, simply comment on the ticket noting the original ticket’s number. For example, you could say “This is a duplicate of issue #42, and can be closed”.
-
-
-# Adding new features
-
-If you would like to add a new feature to Bundler, please follow these steps:
-
-  1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) in the bundler-features repo to discuss your feature.
-  2. Base your commits on the master branch, since we follow [SemVer](http://semver.org) and don't add new features to old releases.
-  3. Commit the code and at least one test covering your changes to a feature branch in your fork.
-  4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the "Features" heading.
-  5. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your feature branch.
-
-If you don't hear back immediately, don’t get discouraged! We all have day jobs, but we respond to most tickets within a day or two.
-
-
-# Beta testing
-
-Early releases require heavy testing, especially across various system setups. We :heart: testers, and are big fans of anyone who can run `gem install bundler --pre` and try out upcoming releases in their development and staging environments.
-
-There may not always be prereleases or beta versions of Bundler. That said, you are always welcome to try checking out master and building a gem yourself if you want to try out the latest changes.
-
-
-# Translations
-
-We don't currently have any translations, but please reach out to us if you would like to help get this going.
-
-
-# Documentation
-
-Code needs explanation, and sometimes those who know the code well have trouble explaining it to someone just getting into it. Because of that, we welcome documentation suggestions and patches from everyone, especially if they are brand new to using Bundler.
-
-Bundler has two main sources of documentation: the built-in help (including usage information and man pages) and the [Bundler documentation site](http://bundler.io).
-
-If you’d like to submit a patch to the man pages, follow the steps for adding a feature above. All of the man pages are located in the `man` directory. Just use the “Documentation” heading when you describe what you did in the changelog.
-
-If you have a suggestion or proposed change for [bundler.io](http://bundler.io), please open an issue or send a pull request to the [bundler-site](https://github.com/bundler/bundler-site) repository.
-
-
-# Community
-
-Community is an important part of all we do. If you’d like to be part of the Bundler community, you can jump right in and start helping make Bundler better for everyone who uses it.
-
-It would be tremendously helpful to have more people answering questions about Bundler (and often simply about Rubygems or Ruby itself) in our [issue tracker](https://github.com/bundler/bundler/issues) or on [Stack Overflow](http://stackoverflow.com/questions/tagged/bundler).
-
-Additional documentation and explanation is always helpful, too. If you have any suggestions for the Bundler website [bundler.io](http://bundler.io), we would absolutely love it if you opened an issue or pull request on the [bundler-site](https://github.com/bundler/bundler-site) repository.
-
-Finally, sharing your experiences and discoveries by writing them up is a valuable way to help others who have similar problems or experiences in the future. You can write a blog post, create an example and commit it to Github, take screenshots, or make videos.
-
-Examples of how Bundler is used help everyone, and we’ve discovered that people already use it in ways that we never imagined when we were writing it. If you’re still not sure what to write about, there are also several projects doing interesting things based on Bundler. They could probably use publicity too.
-
-If you let someone on the core team know you wrote about Bundler, we will add your post to the list of Bundler resources on the Github project wiki.
-
-Finally, participate carefully in the  all contributors to the Bundler project must agree to the contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.

data/ISSUES.md

@@ -1,96 +0,0 @@
-# Bundler Issues
-
-So! You're having problems with Bundler. This file is here to help. If you're running into an error, try reading the rest of this file for help. If you can't figure out how to solve your problem, there are also instructions on how to report a bug.
-
-**Please use the [Bundler
-Features](https://github.com/bundler/bundler-features) repo to suggest and
-discuss features. The bundler issue tracker is only for bugs.**
-
-## Documentation
-
-Instructions for common Bundler uses can be found on the [Bundler documentation site](http://bundler.io/).
-
-Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/man/bundle.1.html).
-
-## Troubleshooting
-
-### Heroku errors
-
-Please open a ticket with Heroku if you're having trouble deploying. They have a professional support team who can help you resolve Heroku issues far better than the Bundler team can. If the problem that you are having turns out to be a bug in Bundler itself, Heroku support can get the exact details to us.
-
-### Other problems
-
-First, figure out exactly what it is that you're trying to do. Then, go to the [Bundler documentation website](http://bundler.io) and see if we have instructions on how to do that.
-
-Second, check [the compatibility
-list](http://bundler.io/compatibility.html), and make sure that the version of Bundler that you are
-using works with the versions of Ruby and Rubygems that you are using.
-
-If the instructions don't work, or you can't find any instructions, you can try these troubleshooting steps:
-
-    # remove user-specific gems and git repos
-    rm -rf ~/.bundle/ ~/.gem/bundler/ ~/.gems/cache/bundler/
-
-    # remove system-wide git repos and git checkouts
-    rm -rf $GEM_HOME/bundler/ $GEM_HOME/cache/bundler/
-
-    # remove project-specific settings
-    rm -rf .bundle/
-
-    # remove project-specific cached gems and repos
-    rm -rf vendor/cache/
-
-    # remove the saved resolve of the Gemfile
-    rm -rf Gemfile.lock
-
-    # uninstall the rubygems-bundler and open_gem gems
-    rvm gemset use global # if using rvm
-    gem uninstall rubygems-bundler open_gem
-
-    # try to install one more time
-    bundle install
-
-## Reporting unresolved problems
-
-Hopefully the troubleshooting steps above resolved your problem. If things still aren't working the way you expect them to, please let us know so that we can diagnose and hopefully fix the problem you're having.
-
-**The best way to report a bug is by providing a reproduction script.** See these examples:
-
-* [Git environment variables causing install to fail.](https://gist.github.com/xaviershay/6207550)
-* [Multiple gems in a repository cannot be updated independently.](https://gist.github.com/xaviershay/6295889)
-
-A half working script with comments for the parts you were unable to automate is still appreciated.
-
-If you are unable to do that, please include the following information in your report:
-
- - What you're trying to accomplish
- - The command you ran
- - What you expected to happen
- - What actually happened
- - The exception backtrace(s), if any
- - Everything output by running `bundle env`
-
-If your version of Bundler does not have the `bundle env` command, then please include:
-
- - 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 executables (run `gem list rubygems-bundler`)
- - Whether you have the `open_gem` gem, which can cause rake activation conflicts (run `gem list open_gem`)
-
-If you are using Rails 2.3, please also include:
-
-  - Your boot.rb file
-  - Your preinitializer.rb file
-  - Your environment.rb file
-
-
-If you have either `rubygems-bundler` or `open_gem` installed, please try removing them and then following the troubleshooting steps above before opening a new ticket.
-
-[Create a gist](https://gist.github.com) containing all of that information, then visit the [Bundler issue tracker](https://github.com/bundler/bundler/issues) and [create a ticket](https://github.com/bundler/bundler/issues/new) describing your problem and linking to your gist.
-
-Thanks for reporting issues and helping make Bundler better!

data/Rakefile

@@ -1,302 +0,0 @@
-# -*- encoding: utf-8 -*-
-$:.unshift File.expand_path("../lib", __FILE__)
-require 'shellwords'
-require 'benchmark'
-
-RUBYGEMS_REPO = File.expand_path("tmp/rubygems")
-BUNDLER_SPEC = Gem::Specification.load("bundler.gemspec")
-
-def safe_task(&block)
-  yield
-  true
-rescue
-  false
-end
-
-# Benchmark task execution
-module Rake
-  class Task
-    alias_method :real_invoke, :invoke
-
-    def invoke(*args)
-      time = Benchmark.measure(@name) do
-        real_invoke(*args)
-      end
-      puts "#{@name} ran for #{time}"
-    end
-  end
-end
-
-namespace :molinillo do
-  task :namespace do
-    files = Dir.glob('lib/bundler/vendor/Molinillo*/**/*.rb')
-    sh "sed -i.bak 's/Molinillo/Bundler::Molinillo/g' #{files.join(' ')}"
-    sh "rm #{files.join('.bak ')}.bak"
-  end
-
-  task :clean do
-    files = Dir.glob('lib/bundler/vendor/Molinillo*/*', File::FNM_DOTMATCH).reject { |f| %(. .. lib).include? f.split('/').last }
-    puts files
-    sh "rm -r #{files.join(' ')}"
-  end
-
-  task :update, [:tag] => [] do |t, args|
-    tag = args[:tag]
-    Dir.chdir 'lib/bundler/vendor' do
-      `curl -L https://github.com/CocoaPods/molinillo/archive/#{tag}.tar.gz | tar -xz`
-    end
-    Rake::Task['molinillo:namespace'].invoke
-    Rake::Task['molinillo:clean'].invoke
-  end
-end
-
-namespace :thor do
-  task :namespace do
-    files = Dir.glob('lib/bundler/vendor/thor*/**/*.rb')
-    sh "sed -i.bak 's/Thor/Bundler::Thor/g' #{files.join(' ')}"
-    sh "rm #{files.join('.bak ')}.bak"
-  end
-
-  task :clean do
-    files = Dir.glob('lib/bundler/vendor/thor*/*', File::FNM_DOTMATCH).reject { |f| %(. .. lib).include? f.split('/').last }
-    puts files
-    sh "rm -r #{files.join(' ')}"
-  end
-
-  task :update, [:tag] => [] do |t, args|
-    tag = args[:tag]
-    Dir.chdir 'lib/bundler/vendor' do
-      `curl -L https://github.com/erikhuda/thor/archive/#{tag}.tar.gz | tar -xz`
-    end
-    Rake::Task['thor:namespace'].invoke
-    Rake::Task['thor:clean'].invoke
-  end
-end
-
-namespace :spec do
-  desc "Ensure spec dependencies are installed"
-  task :deps do
-    deps = Hash[BUNDLER_SPEC.development_dependencies.map do |d|
-      [d.name, d.requirement.to_s]
-    end]
-
-    # JRuby can't build ronn or rdiscount, so we skip that
-    if defined?(RUBY_ENGINE) && RUBY_ENGINE == 'jruby'
-      deps.delete("ronn")
-      deps.delete("rdiscount")
-    end
-
-    deps.sort_by{|name, _| name }.each do |name, version|
-      sh "#{Gem.ruby} -S gem list -i '^#{name}$' -v '#{version}' || " \
-         "#{Gem.ruby} -S gem install #{name} -v '#{version}' --no-ri --no-rdoc"
-    end
-
-    # Download and install gems used inside tests
-    $LOAD_PATH.unshift("./spec")
-    require 'support/rubygems_ext'
-    Spec::Rubygems.setup
-  end
-
-  namespace :travis do
-    task :deps do
-      # Give the travis user a name so that git won't fatally error
-      system "sudo sed -i 's/1000::/1000:Travis:/g' /etc/passwd"
-      # Strip secure_path so that RVM paths transmit through sudo -E
-      system "sudo sed -i '/secure_path/d' /etc/sudoers"
-      # Install groff for the ronn gem
-      sh "sudo apt-get install groff -y"
-      if RUBY_VERSION < '1.9'
-        # Downgrade Rubygems on 1.8 so Ronn can be required
-        # https://github.com/rubygems/rubygems/issues/784
-        sh "gem update --system 2.1.11"
-      else
-        # Downgrade Rubygems so RSpec 3 can be installed
-        # https://github.com/rubygems/rubygems/issues/813
-        sh "gem update --system 2.2.0"
-      end
-      # Install the other gem deps, etc.
-      Rake::Task["spec:deps"].invoke
-    end
-  end
-end
-
-begin
-  rspec = BUNDLER_SPEC.development_dependencies.find{|d| d.name == "rspec" }
-  gem 'rspec', rspec.requirement.to_s
-  require 'rspec/core/rake_task'
-
-  desc "Run specs"
-  RSpec::Core::RakeTask.new
-  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
-
-    # Rubygems specs by version
-    namespace :rubygems do
-      rubyopt = ENV["RUBYOPT"]
-      # When editing this list, also edit .travis.yml!
-      branches = %w(master)
-      releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.3 v2.4.6)
-      (branches + releases).each do |rg|
-        desc "Run specs with Rubygems #{rg}"
-        RSpec::Core::RakeTask.new(rg) do |t|
-          t.rspec_opts = %w(--format documentation --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?(RUBYGEMS_REPO)
-            system("git clone https://github.com/rubygems/rubygems.git tmp/rubygems")
-          end
-          hash = nil
-
-          Dir.chdir(RUBYGEMS_REPO) do
-            system("git remote update")
-            if rg == "master"
-              system("git checkout origin/master")
-            else
-              system("git checkout #{rg}") || raise("Unknown Rubygems ref #{rg}")
-            end
-            hash = `git rev-parse HEAD`.chomp
-          end
-
-          puts "Checked out rubygems '#{rg}' at #{hash}"
-          ENV["RUBYOPT"] = "-I#{File.expand_path("tmp/rubygems/lib")} #{rubyopt}"
-          puts "RUBYOPT=#{ENV['RUBYOPT']}"
-        end
-
-        task rg => ["man:build", "clone_rubygems_#{rg}"]
-        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(--format documentation --color)
-        t.ruby_opts  = %w(-w)
-      end
-
-      task "setup_co" do
-        rg = File.expand_path ENV['RG']
-        puts "Running specs against Rubygems in #{rg}..."
-        ENV["RUBYOPT"] = "-I#{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'] || raise("Rubygems version is required on Travis!")
-
-      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 = system("sudo -E rake spec:rubygems:#{rg}:sudo")
-      # clean up by chowning the newly root-owned tmp directory back to the travis user
-      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 }
-
-      {"specs" => specs, "sudo" => sudos, "realworld" => realworld}.each do |name, passed|
-        if passed
-          puts "\e[0;32m[Travis CI] #{name} passed\e[m"
-        else
-          puts "\e[0;31m[Travis CI] #{name} failed\e[m"
-        end
-      end
-
-      unless specs && sudos && realworld
-        fail "Spec run failed, please review the log for more information"
-      end
-    end
-  end
-
-rescue LoadError
-  task :spec do
-    abort "Run `rake spec:deps` to be able to run the specs"
-  end
-end
-
-begin
-  require 'ronn'
-
-  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
-
-rescue LoadError
-  namespace :man do
-    task(:build) { warn "Install the ronn gem to be able to release!" }
-    task(:clean) { warn "Install the ronn gem to be able to release!" }
-  end
-end
-
-desc "Update vendored SSL certs to match the certs vendored by Rubygems"
-task :update_certs => "spec:rubygems:clone_rubygems_master" do
-  require 'bundler/ssl_certs/certificate_manager'
-  Bundler::SSLCerts::CertificateManager.update_from!(RUBYGEMS_REPO)
-end
-
-require 'bundler/gem_tasks'
-task :build => ["man:clean", "man:build"]
-task :release => ["man:clean", "man:build"]
-
-task :default => :spec