bundler 2.1.1 → 2.2.0.rc.2

data/man/bundle-pristine.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PRISTINE" "1" "December 2019" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "October 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-remove.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-REMOVE" "1" "December 2019" "" ""
+.TH "BUNDLE\-REMOVE" "1" "October 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-remove\fR \- Removes gems from the Gemfile

data/man/bundle-show.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-SHOW" "1" "December 2019" "" ""
+.TH "BUNDLE\-SHOW" "1" "October 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem

data/man/bundle-update.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "December 2019" "" ""
+.TH "BUNDLE\-UPDATE" "1" "October 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions

data/man/bundle-viz.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-VIZ" "1" "December 2019" "" ""
+.TH "BUNDLE\-VIZ" "1" "October 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile

data/man/bundle.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE" "1" "December 2019" "" ""
+.TH "BUNDLE" "1" "October 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management

data/man/gemfile.5

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "GEMFILE" "5" "December 2019" "" ""
+.TH "GEMFILE" "5" "October 2020" "" ""
 .
 .SH "NAME"
 \fBGemfile\fR \- A format for describing gem dependencies for Ruby programs
@@ -150,7 +150,7 @@ gem "RedCloth", ">= 4\.1\.0", "< 4\.2\.0"
 .IP "" 0
 .
 .SS "REQUIRE AS"
-Each \fIgem\fR \fBMAY\fR specify files that should be used when autorequiring via \fBBundler\.require\fR\. You may pass an array with multiple files or \fBtrue\fR if file you want \fBrequired\fR has same name as \fIgem\fR or \fBfalse\fR to prevent any file from being autorequired\.
+Each \fIgem\fR \fBMAY\fR specify files that should be used when autorequiring via \fBBundler\.require\fR\. You may pass an array with multiple files or \fBtrue\fR if the file you want \fBrequired\fR has the same name as \fIgem\fR or \fBfalse\fR to prevent any file from being autorequired\.
 .
 .IP "" 4
 .
@@ -227,8 +227,8 @@ To specify multiple groups to ignore, specify a list of groups separated by spac
 .
 .nf
 
-bundle config set without test
-bundle config set without development test
+bundle config set \-\-local without test
+bundle config set \-\-local without development test
 .
 .fi
 .

data/man/gemfile.5.ronn

@@ -120,8 +120,8 @@ Each _gem_ `MAY` have one or more version specifiers.
 ### REQUIRE AS
 
 Each _gem_ `MAY` specify files that should be used when autorequiring via
-`Bundler.require`. You may pass an array with multiple files or `true` if file
-you want `required` has same name as _gem_ or `false` to
+`Bundler.require`. You may pass an array with multiple files or `true` if the file
+you want `required` has the same name as _gem_ or `false` to
 prevent any file from being autorequired.
 
     gem "redis", :require => ["redis/connection/hiredis", "redis"]
@@ -163,8 +163,8 @@ not install with the `without` configuration.
 
 To specify multiple groups to ignore, specify a list of groups separated by spaces.
 
-    bundle config set without test
-    bundle config set without development test
+    bundle config set --local without test
+    bundle config set --local without development test
 
 Also, calling `Bundler.setup` with no parameters, or calling `require "bundler/setup"`
 will setup all groups except for the ones you excluded via `--without` (since they

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bundler
 version: !ruby/object:Gem::Version
-  version: 2.1.1
+  version: 2.2.0.rc.2
 platform: ruby
 authors:
 - André Arko
@@ -22,7 +22,7 @@ authors:
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-12-18 00:00:00.000000000 Z
+date: 2020-10-07 00:00:00.000000000 Z
 dependencies: []
 description: Bundler manages an application's dependencies through its entire life,
   across many machines, systematically and repeatably
@@ -54,6 +54,7 @@ files:
 - lib/bundler/cli/console.rb
 - lib/bundler/cli/doctor.rb
 - lib/bundler/cli/exec.rb
+- lib/bundler/cli/fund.rb
 - lib/bundler/cli/gem.rb
 - lib/bundler/cli/info.rb
 - lib/bundler/cli/init.rb
@@ -164,19 +165,25 @@ files:
 - lib/bundler/templates/newgem/Rakefile.tt
 - lib/bundler/templates/newgem/bin/console.tt
 - lib/bundler/templates/newgem/bin/setup.tt
+- lib/bundler/templates/newgem/circleci/config.yml.tt
 - lib/bundler/templates/newgem/exe/newgem.tt
 - lib/bundler/templates/newgem/ext/newgem/extconf.rb.tt
 - lib/bundler/templates/newgem/ext/newgem/newgem.c.tt
 - lib/bundler/templates/newgem/ext/newgem/newgem.h.tt
+- lib/bundler/templates/newgem/github/workflows/main.yml.tt
 - lib/bundler/templates/newgem/gitignore.tt
+- lib/bundler/templates/newgem/gitlab-ci.yml.tt
 - lib/bundler/templates/newgem/lib/newgem.rb.tt
 - lib/bundler/templates/newgem/lib/newgem/version.rb.tt
 - lib/bundler/templates/newgem/newgem.gemspec.tt
 - lib/bundler/templates/newgem/rspec.tt
+- lib/bundler/templates/newgem/rubocop.yml.tt
 - lib/bundler/templates/newgem/spec/newgem_spec.rb.tt
 - lib/bundler/templates/newgem/spec/spec_helper.rb.tt
-- lib/bundler/templates/newgem/test/newgem_test.rb.tt
-- lib/bundler/templates/newgem/test/test_helper.rb.tt
+- lib/bundler/templates/newgem/test/minitest/newgem_test.rb.tt
+- lib/bundler/templates/newgem/test/minitest/test_helper.rb.tt
+- lib/bundler/templates/newgem/test/test-unit/newgem_test.rb.tt
+- lib/bundler/templates/newgem/test/test-unit/test_helper.rb.tt
 - lib/bundler/templates/newgem/travis.yml.tt
 - lib/bundler/ui.rb
 - lib/bundler/ui/rg_proxy.rb
@@ -268,89 +275,63 @@ files:
 - lib/bundler/worker.rb
 - lib/bundler/yaml_serializer.rb
 - man/bundle-add.1
-- man/bundle-add.1.txt
-- man/bundle-add.ronn
+- man/bundle-add.1.ronn
 - man/bundle-binstubs.1
-- man/bundle-binstubs.1.txt
-- man/bundle-binstubs.ronn
+- man/bundle-binstubs.1.ronn
 - man/bundle-cache.1
-- man/bundle-cache.1.txt
-- man/bundle-cache.ronn
+- man/bundle-cache.1.ronn
 - man/bundle-check.1
-- man/bundle-check.1.txt
-- man/bundle-check.ronn
+- man/bundle-check.1.ronn
 - man/bundle-clean.1
-- man/bundle-clean.1.txt
-- man/bundle-clean.ronn
+- man/bundle-clean.1.ronn
 - man/bundle-config.1
-- man/bundle-config.1.txt
-- man/bundle-config.ronn
+- man/bundle-config.1.ronn
 - man/bundle-doctor.1
-- man/bundle-doctor.1.txt
-- man/bundle-doctor.ronn
+- man/bundle-doctor.1.ronn
 - man/bundle-exec.1
-- man/bundle-exec.1.txt
-- man/bundle-exec.ronn
+- man/bundle-exec.1.ronn
 - man/bundle-gem.1
-- man/bundle-gem.1.txt
-- man/bundle-gem.ronn
+- man/bundle-gem.1.ronn
 - man/bundle-info.1
-- man/bundle-info.1.txt
-- man/bundle-info.ronn
+- man/bundle-info.1.ronn
 - man/bundle-init.1
-- man/bundle-init.1.txt
-- man/bundle-init.ronn
+- man/bundle-init.1.ronn
 - man/bundle-inject.1
-- man/bundle-inject.1.txt
-- man/bundle-inject.ronn
+- man/bundle-inject.1.ronn
 - man/bundle-install.1
-- man/bundle-install.1.txt
-- man/bundle-install.ronn
+- man/bundle-install.1.ronn
 - man/bundle-list.1
-- man/bundle-list.1.txt
-- man/bundle-list.ronn
+- man/bundle-list.1.ronn
 - man/bundle-lock.1
-- man/bundle-lock.1.txt
-- man/bundle-lock.ronn
+- man/bundle-lock.1.ronn
 - man/bundle-open.1
-- man/bundle-open.1.txt
-- man/bundle-open.ronn
+- man/bundle-open.1.ronn
 - man/bundle-outdated.1
-- man/bundle-outdated.1.txt
-- man/bundle-outdated.ronn
+- man/bundle-outdated.1.ronn
 - man/bundle-platform.1
-- man/bundle-platform.1.txt
-- man/bundle-platform.ronn
+- man/bundle-platform.1.ronn
 - man/bundle-pristine.1
-- man/bundle-pristine.1.txt
-- man/bundle-pristine.ronn
+- man/bundle-pristine.1.ronn
 - man/bundle-remove.1
-- man/bundle-remove.1.txt
-- man/bundle-remove.ronn
+- man/bundle-remove.1.ronn
 - man/bundle-show.1
-- man/bundle-show.1.txt
-- man/bundle-show.ronn
+- man/bundle-show.1.ronn
 - man/bundle-update.1
-- man/bundle-update.1.txt
-- man/bundle-update.ronn
+- man/bundle-update.1.ronn
 - man/bundle-viz.1
-- man/bundle-viz.1.txt
-- man/bundle-viz.ronn
+- man/bundle-viz.1.ronn
 - man/bundle.1
-- man/bundle.1.txt
-- man/bundle.ronn
+- man/bundle.1.ronn
 - man/gemfile.5
 - man/gemfile.5.ronn
-- man/gemfile.5.txt
-- man/index.txt
 homepage: https://bundler.io
 licenses:
 - MIT
 metadata:
-  bug_tracker_uri: https://github.com/bundler/bundler/issues
-  changelog_uri: https://github.com/bundler/bundler/blob/master/CHANGELOG.md
+  bug_tracker_uri: https://github.com/rubygems/rubygems/issues?q=is%3Aopen+is%3Aissue+label%3ABundler
+  changelog_uri: https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md
   homepage_uri: https://bundler.io/
-  source_code_uri: https://github.com/bundler/bundler/
+  source_code_uri: https://github.com/rubygems/rubygems/
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -366,7 +347,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: 2.5.2
 requirements: []
-rubygems_version: 3.1.1
+rubygems_version: 3.2.0.rc.1
 signing_key: 
 specification_version: 4
 summary: The best way to manage your application's dependencies

data/man/bundle-add.1.txt

@@ -1,58 +0,0 @@
-BUNDLE-ADD(1)							 BUNDLE-ADD(1)
-
-
-
-NAME
-       bundle-add - Add gem to the Gemfile and run bundle install
-
-SYNOPSIS
-       bundle	  add	  GEM_NAME     [--group=GROUP]	   [--version=VERSION]
-       [--source=SOURCE]   [--git=GIT]	 [--branch=BRANCH]    [--skip-install]
-       [--strict] [--optimistic]
-
-DESCRIPTION
-       Adds  the  named  gem  to  the  Gemfile	and run bundle install. bundle
-       install can be avoided by using the flag --skip-install.
-
-       Example:
-
-       bundle add rails
-
-       bundle add rails --version "< 3.0, > 1.1"
-
-       bundle add rails  --version  "~>  5.0.0"  --source  "https://gems.exam-
-       ple.com" --group "development"
-
-       bundle add rails --skip-install
-
-       bundle add rails --group "development, test"
-
-OPTIONS
-       --version, -v
-	      Specify version requirements(s) for the added gem.
-
-       --group, -g
-	      Specify  the  group(s) for the added gem. Multiple groups should
-	      be separated by commas.
-
-       --source, , -s
-	      Specify the source for the added gem.
-
-       --git  Specify the git source for the added gem.
-
-       --branch
-	      Specify the git branch for the added gem.
-
-       --skip-install
-	      Adds the gem to the Gemfile but does not install it.
-
-       --optimistic
-	      Adds optimistic declaration of version
-
-       --strict
-	      Adds strict declaration of version
-
-
-
-
-				 December 2019			 BUNDLE-ADD(1)

data/man/bundle-binstubs.1.txt

@@ -1,48 +0,0 @@
-BUNDLE-BINSTUBS(1)					    BUNDLE-BINSTUBS(1)
-
-
-
-NAME
-       bundle-binstubs - Install the binstubs of the listed gems
-
-SYNOPSIS
-       bundle binstubs GEM_NAME [--force] [--path PATH] [--standalone]
-
-DESCRIPTION
-       Binstubs  are  scripts  that wrap around executables. Bundler creates a
-       small Ruby file (a binstub) that loads Bundler, runs the  command,  and
-       puts  it  into  bin/. Binstubs are a shortcut-or alternative- to always
-       using bundle exec. This gives you a file that can be run directly,  and
-       one  that  will always run the correct gem version used by the applica-
-       tion.
-
-       For example, if you run bundle binstubs rspec-core, Bundler will create
-       the file bin/rspec. That file will contain enough code to load Bundler,
-       tell it to load the bundled gems, and then run rspec.
-
-       This command generates binstubs for executables in  GEM_NAME.  Binstubs
-       are  put into bin, or the --path directory if one has been set. Calling
-       binstubs with [GEM [GEM]] will create binstubs for all given gems.
-
-OPTIONS
-       --force
-	      Overwrite existing binstubs if they exist.
-
-       --path The location to install the specified binstubs to. This defaults
-	      to bin.
-
-       --standalone
-	      Makes  binstubs  that  can work without depending on Rubygems or
-	      Bundler at runtime.
-
-       --shebang
-	      Specify a different shebang executable  name  than  the  default
-	      (default 'ruby')
-
-BUNDLE INSTALL --BINSTUBS
-       To  create  binstubs  for  all  the  gems in the bundle you can use the
-       --binstubs flag in bundle install(1) bundle-install.1.html.
-
-
-
-				 December 2019		    BUNDLE-BINSTUBS(1)

data/man/bundle-cache.1.txt

@@ -1,78 +0,0 @@
-BUNDLE-CACHE(1) 					       BUNDLE-CACHE(1)
-
-
-
-NAME
-       bundle-cache - Package your needed .gem files into your application
-
-SYNOPSIS
-       bundle cache
-
-DESCRIPTION
-       Copy  all of the .gem files needed to run the application into the ven-
-       dor/cache   directory.	In   the   future,   when   running    [bundle
-       install(1)][bundle-install], use the gems in the cache in preference to
-       the ones on rubygems.org.
-
-GIT AND PATH GEMS
-       The bundle cache command can also package :git and  :path  dependencies
-       besides	.gem  files. This needs to be explicitly enabled via the --all
-       option. Once used, the --all option will be remembered.
-
-SUPPORT FOR MULTIPLE PLATFORMS
-       When using gems that have different packages for  different  platforms,
-       Bundler	supports caching of gems for other platforms where the Gemfile
-       has been resolved (i.e. present in the lockfile) in vendor/cache.  This
-       needs  to  be enabled via the --all-platforms option. This setting will
-       be remembered in your local bundler configuration.
-
-REMOTE FETCHING
-       By default, if you run bundle install(1)](bundle-install.1.html)  after
-       running bundle cache(1) bundle-cache.1.html, bundler will still connect
-       to rubygems.org to check whether a platform-specific gem exists for any
-       of the gems in vendor/cache.
-
-       For instance, consider this Gemfile(5):
-
-
-
-	   source "https://rubygems.org"
-
-	   gem "nokogiri"
-
-
-
-       If you run bundle cache under C Ruby, bundler will retrieve the version
-       of nokogiri for the "ruby" platform. If you deploy  to  JRuby  and  run
-       bundle  install,  bundler  is  forced  to check to see whether a "java"
-       platformed nokogiri exists.
-
-       Even though the nokogiri gem  for  the  Ruby  platform  is  technically
-       acceptable  on  JRuby, it has a C extension that does not run on JRuby.
-       As a result, bundler will, by default, still connect to rubygems.org to
-       check  whether  it  has	a version of one of your gems more specific to
-       your platform.
-
-       This problem is also not limited to  the  "java"  platform.  A  similar
-       (common) problem can happen when developing on Windows and deploying to
-       Linux, or even when developing on OSX and deploying to Linux.
-
-       If you know for sure that the gems packaged in vendor/cache are	appro-
-       priate  for the platform you are on, you can run bundle install --local
-       to skip checking for more appropriate gems, and use the	ones  in  ven-
-       dor/cache.
-
-       One  way  to be sure that you have the right platformed versions of all
-       your gems is to run bundle cache on an identical machine and  check  in
-       the  gems. For instance, you can run bundle cache on an identical stag-
-       ing box during your staging process,  and  check  in  the  vendor/cache
-       before deploying to production.
-
-       By  default,  bundle  cache(1)  bundle-cache.1.html  fetches  and  also
-       installs the gems to the default location. To package the  dependencies
-       to  vendor/cache without installing them to the local install location,
-       you can run bundle cache --no-install.
-
-
-
-				 December 2019		       BUNDLE-CACHE(1)