bundler 1.15.4 → 1.16.0.pre.1

data/bin/rake

@@ -1,19 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  begin
-    gem dep.name, dep.requirement
-  rescue Gem::LoadError => e
-    $stderr.puts "#{e.message} (#{e.class})"
-  end
-end
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rake", "rake")

data/bin/rspec

@@ -1,15 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  gem dep.name, dep.requirement
-end
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rspec-core", "rspec")

data/bin/rubocop

@@ -1,17 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  gem dep.name, dep.requirement
-end
-
-gem "rubocop", "= 0.48.0"
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rubocop", "rubocop")

data/bin/with_rubygems

@@ -1,39 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "pathname"
-
-def run(*cmd)
-  return if system(*cmd)
-  raise "Running `#{cmd.join(" ")}` failed"
-end
-
-version = ENV.delete("RGV")
-rubygems_path = Pathname.new(__FILE__).join("../../tmp/rubygems").expand_path
-unless rubygems_path.directory?
-  rubygems_path.parent.mkpath unless rubygems_path.directory?
-  run("git", "clone", "https://github.com/rubygems/rubygems.git", rubygems_path.to_s)
-end
-Dir.chdir(rubygems_path) do
-  version = "v#{version}" if version =~ /\A\d/
-  run("git", "checkout", version, "--quiet")
-end if version
-
-rubygems_lib = rubygems_path + "lib"
-ENV["RUBYOPT"] = %(-I#{rubygems_lib} #{ENV["RUBYOPT"]})
-
-if $0 != __FILE__
-  ARGV.unshift($0)
-elsif cmd = ARGV.first
-  possible_dirs = [
-    Pathname.new(__FILE__) + "..",
-    Pathname.new(__FILE__) + "../../exe",
-    rubygems_path + "bin",
-  ]
-  cmd = possible_dirs.map do |dir|
-    dir.join(cmd).expand_path
-  end.find(&:file?)
-  ARGV[0] = cmd.to_s if cmd
-end
-
-exec(*ARGV)

data/bundler.gemspec

@@ -1,48 +0,0 @@
-# coding: utf-8
-# frozen_string_literal: true
-lib = File.expand_path("../lib/", __FILE__)
-$:.unshift lib unless $:.include?(lib)
-require "bundler/version"
-
-Gem::Specification.new do |s|
-  s.name        = "bundler"
-  s.version     = Bundler::VERSION
-  s.license     = "MIT"
-  s.authors     = [
-    "André Arko", "Samuel Giddins", "Chris Morris", "James Wen", "Tim Moore",
-    "André Medeiros", "Jessica Lynn Suttles", "Terence Lee", "Carl Lerche",
-    "Yehuda Katz"
-  ]
-  s.email       = ["team@bundler.io"]
-  s.homepage    = "http://bundler.io"
-  s.summary     = "The best way to manage your application's dependencies"
-  s.description = "Bundler manages an application's dependencies through its entire life, across many machines, systematically and repeatably"
-
-  if s.respond_to?(:metadata=)
-    s.metadata = {
-      "bug_tracker_uri" => "http://github.com/bundler/bundler/issues",
-      "changelog_uri" => "https://github.com/bundler/bundler/blob/master/CHANGELOG.md",
-      "homepage_uri" => "https://bundler.io/",
-      "source_code_uri" => "http://github.com/bundler/bundler/",
-    }
-  end
-
-  s.required_ruby_version     = ">= 1.8.7"
-  s.required_rubygems_version = ">= 1.3.6"
-
-  s.add_development_dependency "automatiek", "~> 0.1.0"
-  s.add_development_dependency "mustache",   "0.99.6"
-  s.add_development_dependency "rake",       "~> 10.0"
-  s.add_development_dependency "rdiscount",  "~> 2.2"
-  s.add_development_dependency "ronn",       "~> 0.7.3"
-  s.add_development_dependency "rspec",      "~> 3.5"
-
-  s.files = `git ls-files -z`.split("\x0").reject {|f| f.match(%r{^(test|spec|features)/}) }
-  # we don't check in man pages, but we need to ship them because
-  # we use them to generate the long-form help for each command.
-  s.files += Dir.glob("man/**/*")
-
-  s.bindir        = "exe"
-  s.executables   = %w(bundle bundler)
-  s.require_paths = ["lib"]
-end

data/doc/README.md

@@ -1,30 +0,0 @@
-# Docs: Contributing and developing Bundler
-
-_If you're looking for documentation on how to use Bundler: visit [bundler.io](http://bundler.io/), or run `bundle help` from the command line. You may also be interested in [troubleshooting common issues](TROUBLESHOOTING.md) found when using Bundler._
-
-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! Thanks for helping us make Bundler better.
-
-## Contributing
-
-* [Overview & getting started](contributing/README.md)
-* [How you can help: your first contributions!](contributing/HOW_YOU_CAN_HELP.md)
-* [Bug triage](contributing/BUG_TRIAGE.md)
-* [Getting help](contributing/GETTING_HELP.md)
-* [Filing issues](contributing/ISSUES.md)
-* [Community](contributing/COMMUNITY.md)
-
-## Development
-
-* [Overview](development/README.md)
-* [Development setup](development/SETUP.md)
-* [Submitting pull requests](development/PULL_REQUESTS.md)
-* [Adding new features](development/NEW_FEATURES.md)
-* [Releasing Bundler](development/RELEASING.md)
-
-## Documentation
-
-* [Overview](documentation/README.md)
-* [Writing docs for man pages](documentation/WRITING.md)
-* [Documentation vision](documentation/VISION.md)

data/doc/TROUBLESHOOTING.md

@@ -1,64 +0,0 @@
-# Troubleshooting common issues
-
-Stuck using Bundler? Browse these common issues before [filing a new issue](contributing/ISSUES.md).
-
-## Permission denied when installing bundler
-
-Certain operating systems such as MacOS and Ubuntu have versions of Ruby that require elevated privileges to install gems.
-
-    ERROR:  While executing gem ... (Gem::FilePermissionError)
-      You don't have write permissions for the /Library/Ruby/Gems/2.0.0 directory.
-
-There are multiple ways to solve this issue. You can install bundler with elevated privilges using `sudo` or `su`.
-
-    sudo gem install bundler
-
-If you cannot elevated your privileges or do not want to globally install Bundler, you can use the `--user-install` option.
-
-    gem install bundler --user-install
-
-This will install Bundler into your home directory. Note that you will need to append `~/.gem/ruby/<ruby version>/bin` to your `$PATH` variable to use `bundle`.
-
-## Heroku errors
-
-Please open a ticket with [Heroku](https://www.heroku.com) 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](https://www.heroku.com/support) can get the exact details to us.
-
-## Other problems
-
-First, figure out exactly what it is that you're trying to do (see [XY Problem](http://xyproblem.info/)). 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. To see your versions:
-
-    # Bundler version
-    bundle -v
-
-    # Ruby version
-    ruby -v
-
-    # Rubygems version
-    gem -v
-
-If these instructions don't work, or you can't find any appropriate 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

data/doc/contributing/BUG_TRIAGE.md

@@ -1,36 +0,0 @@
-# Bug triage
-
-Triaging is the work of processing tickets that have been opened by users. Common tasks include verifying bugs, categorizing tickets, 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](ISSUES.md) to walk users through the process of how to report an issue with the Bundler project. We also have a [troubleshooting guide](../TROUBLESHOOTING.md) to diagnose common problems.
-
-Not every ticket will be a bug in Bundler's code, but open tickets usually mean that the there is something we could improve to help that user. Sometimes that means writing additional documentation or making error messages clearer.
-
-## Triaging existing issues
-
-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 the bug clearly documented 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 the issue, chances are good that the bug has been fixed already (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 your triaged bug
-
-Everyone is welcome and encouraged to fix any open bug, improve an error message or add documentation. If you have a fix or an improvement to a ticket that you would like to contribute, we have a small guide to help:
-
-  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. Review the [pull request guide](../development/PULL_REQUESTS.md).
-  4. Commit the code with at least one test covering your changes to a named branch in your fork.
-  5. Put a line in the [CHANGELOG](../../CHANGELOG.md) summarizing your changes under the next release under the “Bugfixes” heading.
-  6. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your bugfix branch.
-
-## Duplicates!
-
-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”.

data/doc/contributing/COMMUNITY.md

@@ -1,13 +0,0 @@
-# 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](https://github.com/rubygems/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.
-
-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.
-
-Publishing examples of how Bundler is used helps 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.
-
-Finally, 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/doc/contributing/GETTING_HELP.md

@@ -1,11 +0,0 @@
-# Getting help
-
-If you have any questions after reading the documentation for contributing, please feel free to contact either [@indirect](https://github.com/indirect), [@segiddins](https://github.com/segiddins), or [@RochesterinNYC](https://github.com/RochesterinNYC). They are all happy to provide help working through your first bug fix or thinking through the problem you’re trying to resolve.
-
-The best ways to get in touch are:
-
-* [Bundler Slack](https://bundler.slack.com).
-  * Not a member of the Slack? Join the Bundler team slack [here](http://slack.bundler.io/)!
-* [Bundler mailing list](http://groups.google.com/group/ruby-bundler)
-
-You may also find our guide on [filing issues](ISSUES.md) to be helpful as well!

data/doc/contributing/HOW_YOU_CAN_HELP.md

@@ -1,27 +0,0 @@
-# How you can help: your first commits!
-
-If you’re interested in contributing to Bundler, that’s awesome! We’d love your help.
-
-If at any point you get stuck, here's how to [get in touch with the Bundler team for help](GETTING_HELP.md).
-
-## First contribution suggestions
-
-We track [small bugs and features](https://github.com/bundler/bundler/labels/contribution%3A%20small) so that anyone who wants to help can start with something that's not too overwhelming.
-
-Generally, great ways to get started helping out with Bundler are:
-
-  - using prerelease versions (run `gem install bundler --pre`)
-  - [reporting bugs you encounter or suggesting new features](https://github.com/bundler/bundler/issues/new)
-    - see our [issues guide](ISSUES.md) for help on filing issues
-    - see the [new features documentation](../development/NEW_FEATURES.md) for more
-  - adding to or editing [the Bundler documentation website](http://bundler.io) and [Bundler man pages](http://bundler.io/man/bundle.1.html)
-  - [checking issues for completeness](BUG_TRIAGE.md)
-  - closing issues that are not complete
-  - adding a failing test for reproducible [reported bugs](https://github.com/bundler/bundler/issues)
-  - reviewing [pull requests](https://github.com/bundler/bundler/pulls) and suggesting improvements
-  - improving existing code, including suggestions from [PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master) or [CodeClimate](https://codeclimate.com/github/bundler/bundler)
-  - writing code (no patch is too small! fix typos or bad whitespace)
-    - get started setting up your dev environment with [these instructions](../development/DEVELOPMENT_SETUP.md)
-  - backfilling [unit tests](https://github.com/bundler/bundler/tree/master/spec/bundler) for modules that lack [coverage](https://codeclimate.com/github/bundler/bundler/coverage)
-
-If nothing on those lists looks good, [talk to us](http://slack.bundler.io/), and we'll figure out what you can help with. We can absolutely use your help, no matter what level of programming skill you have at the moment.

data/doc/contributing/ISSUES.md

@@ -1,51 +0,0 @@
-# Filing Issues: a guide
-
-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.
-
-Before filing an issue, check our [troubleshooting guide](../TROUBLESHOOTING.md) for quick fixes to common issues.
-
-## 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) or [Bundler Command Line Reference](http://bundler.io/v1.11/commands.html).
-
-## Reporting unresolved problems
-
-Check our [troubleshooting common issues guide](../TROUBLESHOOTING.md) and see if your issues is resolved using the steps provided.
-
-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 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/doc/contributing/README.md

@@ -1,38 +0,0 @@
-# Contributing to Bundler
-
-Welcome to Bundler! We are so happy that you're here. We know it can be daunting to joining a new open source project, so here's a quick overview of what you can expect from this documentation.
-
-*Something missing?* Send us a [pull request](../development/PULL_REQUESTS.md)!
-
-**Recommended first steps**
-
-- Join us in the Bundler slack! Generate an invite [here](http://slack.bundler.io/)
-- *If you're interested in helping with code:*
-  - Get a quick overview of our [development process](../development/README.md)
-  - [Setup your machine for development](../development/SETUP.md)
-  - Checkout [How you can help: your first contributions!](HOW_YOU_CAN_HELP.md) for a list of suggestions to get started
-- *If you're interested in helping with documentation:*
-  - Read up on [how documentation works for Bundler](../documentation/README.md)
-  - Learn about our [documentation vision](../documentation/VISION.md)
-
-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).
-
-## [How you can help: your first contributions!](HOW_YOU_CAN_HELP.md)
-
-A detailed overview of how to get started contributing to Bundler, including a long list of suggestions for your first project.
-
-## [Bug triage](BUG_TRIAGE.md)
-
-Want to take a stab at processing issues? Start here.
-
-## [Getting help](GETTING_HELP.md)
-
-How to get in touch with folks who can help when you're stuck. Don't worry! This happens to all of us. We're really nice, we promise.
-
-## [Filing issues](ISSUES.md)
-
-We see a lot of issues in the Bundler repo! Use this guide to file informative, actionable issues.
-
-## [Community](COMMUNITY.md)
-
-Learn more about our goals for the Bundler community and the ways you can help us build better together.

data/doc/development/NEW_FEATURES.md

@@ -1,10 +0,0 @@
-# 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/issues/new) with the [`feature-request` label](https://github.com/bundler/bundler/labels/type:%20feature-request) 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. Send us a [pull request](PULL_REQUESTS.md) 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.

data/doc/development/PULL_REQUESTS.md

@@ -1,40 +0,0 @@
-# Submitting Pull Requests
-
-Before you submit a pull request, please remember to do the following:
-
-1. Check your code format and style
-2. Run the test suite
-3. Use a meaningful commit message without tags
-
-## Code formatting
-
-Make sure the code formatting and styling adheres to the guidelines. We use RuboCop for this. Lack of formatting adherence will result in automatic Travis build failures.
-
-      $ bin/rubocop -a
-
-## Tests
-
-Prior to submitting your PR, please run the test suite:
-
-      $ bin/rspec
-
-If you are unable to run the entire test suite, please run the unit test suite and at least the integration specs related to the command or domain of Bundler that your code changes relate to.
-
-Ex. For a pull request that changes something with `bundle update`, you might run:
-
-      $ bin/rspec spec/bundler
-      $ bin/rspec spec/commands/update_spec.rb
-
-## Commit messages
-
-Please ensure that the commit messages included in the pull request __do not__ have the following:
-  - `@tag` GitHub user or team references (ex. `@indirect` or `@bundler/core`)
-  - `#id` references to issues or pull requests (ex. `#43` or `bundler/bundler-site#12`)
-
-If you want to use these mechanisms, please instead include them in the pull request description. This prevents multiple notifications or references being created on commit rebases or pull request/branch force pushes.
-
-Additionally, do not use `[ci skip]` or `[skip ci]` mechanisms in your pull request titles/descriptions or commit messages. Every potential commit and pull request should run through Bundler's CI system. This applies to all changes/commits (ex. even a change to just documentation or the removal of a comment).
-
-## CHANGELOG.md
-
-Don't forget to add your changes into the CHANGELOG! If you're submitting documentation, note the changes under the "Documentation" heading.