bundler 1.16.6 → 1.17.0.pre.1

data/man/bundle-config.ronn

@@ -170,6 +170,8 @@ learn more about their operation in [bundle install(1)](bundle-install.1.html).
    When set, Gemfiles containing multiple sources will produce errors
    instead of warnings.
    Use `bundle config --delete disable_multisource` to unset.
+* `disable_platform_warnings` (`BUNDLE_DISABLE_PLATFORM_WARNINGS`):
+   Disable warnings during bundle install when a dependency is unused on the current platform.
 * `disable_shared_gems` (`BUNDLE_DISABLE_SHARED_GEMS`):
    Stop Bundler from accessing gems installed to RubyGems' normal location.
 * `disable_version_check` (`BUNDLE_DISABLE_VERSION_CHECK`):
@@ -196,6 +198,9 @@ learn more about their operation in [bundle install(1)](bundle-install.1.html).
 * `global_gem_cache` (`BUNDLE_GLOBAL_GEM_CACHE`):
    Whether Bundler should cache all gems globally, rather than locally to the
    installing Ruby installation.
+* `global_path_appends_ruby_scope` (`BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE`):
+   Whether Bundler should append the Ruby scope (e.g. engine and ABI version)
+   to a globally-configured path.
 * `ignore_messages` (`BUNDLE_IGNORE_MESSAGES`): When set, no post install
    messages will be printed. To silence a single gem, use dot notation like
    `ignore_messages.httparty true`.
@@ -222,6 +227,8 @@ learn more about their operation in [bundle install(1)](bundle-install.1.html).
    is used, defaults to vendor/bundle.
 * `path.system` (`BUNDLE_PATH__SYSTEM`):
    Whether Bundler will install gems into the default system path (`Gem.dir`).
+* `path_relative_to_cwd` (`PATH_RELATIVE_TO_CWD`)
+   Makes `--path` relative to the CWD instead of the `Gemfile`.
 * `plugins` (`BUNDLE_PLUGINS`):
    Enable Bundler's experimental plugin system.
 * `prefer_gems_rb` (`BUNDLE_PREFER_GEMS_RB`)

data/man/bundle-doctor.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-DOCTOR" "1" "October 2018" "" ""
+.TH "BUNDLE\-DOCTOR" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-doctor\fR \- Checks the bundle for common problems

data/man/bundle-doctor.1.txt

@@ -41,4 +41,4 @@ OPTIONS
 
 
 
-				 October 2018		      BUNDLE-DOCTOR(1)
+				September 2018		      BUNDLE-DOCTOR(1)

data/man/bundle-exec.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-EXEC" "1" "October 2018" "" ""
+.TH "BUNDLE\-EXEC" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-exec\fR \- Execute a command in the context of the bundle

data/man/bundle-exec.1.txt

@@ -175,4 +175,4 @@ RUBYGEMS PLUGINS
 
 
 
-				 October 2018			BUNDLE-EXEC(1)
+				September 2018			BUNDLE-EXEC(1)

data/man/bundle-gem.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-GEM" "1" "October 2018" "" ""
+.TH "BUNDLE\-GEM" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem

data/man/bundle-gem.1.txt

@@ -88,4 +88,4 @@ SEE ALSO
 
 
 
-				 October 2018			 BUNDLE-GEM(1)
+				September 2018			 BUNDLE-GEM(1)

data/man/bundle-info.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INFO" "1" "October 2018" "" ""
+.TH "BUNDLE\-INFO" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-info\fR \- Show information for the given gem in your bundle

data/man/bundle-info.1.txt

@@ -18,4 +18,4 @@ OPTIONS
 
 
 
-				 October 2018			BUNDLE-INFO(1)
+				September 2018			BUNDLE-INFO(1)

data/man/bundle-init.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INIT" "1" "October 2018" "" ""
+.TH "BUNDLE\-INIT" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-init\fR \- Generates a Gemfile into the current working directory

data/man/bundle-init.1.txt

@@ -31,4 +31,4 @@ SEE ALSO
 
 
 
-				 October 2018			BUNDLE-INIT(1)
+				September 2018			BUNDLE-INIT(1)

data/man/bundle-inject.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INJECT" "1" "October 2018" "" ""
+.TH "BUNDLE\-INJECT" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile

data/man/bundle-inject.1.txt

@@ -29,4 +29,4 @@ DESCRIPTION
 
 
 
-				 October 2018		      BUNDLE-INJECT(1)
+				September 2018		      BUNDLE-INJECT(1)

data/man/bundle-install.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INSTALL" "1" "October 2018" "" ""
+.TH "BUNDLE\-INSTALL" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-install\fR \- Install the dependencies specified in your Gemfile
@@ -221,10 +221,7 @@ Bundler uses this file in all subsequent calls to \fBbundle install\fR, which gu
 Because of the way dependency resolution works, even a seemingly small change (for instance, an update to a point\-release of a dependency of a gem in your Gemfile(5)) can result in radically different gems being needed to satisfy all dependencies\.
 .
 .P
-As a result, you \fBSHOULD\fR check your \fBGemfile\.lock\fR into version control, in both applications and gems\. If you do not, every machine that checks out your repository (including your production server) will resolve all dependencies again, which will result in different versions of third\-party code being used if \fBany\fR of the gems in the Gemfile(5) or any of their dependencies have been updated\.
-.
-.P
-When Bundler first shipped, the \fBGemfile\.lock\fR was included in the \fB\.gitignore\fR file included with generated gems\. Over time, however, it became clear that this practice forces the pain of broken dependencies onto new contributors, while leaving existing contributors potentially unaware of the problem\. Since \fBbundle install\fR is usually the first step towards a contribution, the pain of broken dependencies would discourage new contributors from contributing\. As a result, we have revised our guidance for gem authors to now recommend checking in the lock for gems\.
+As a result, you \fBSHOULD\fR check your \fBGemfile\.lock\fR into version control\. If you do not, every machine that checks out your repository (including your production server) will resolve all dependencies again, which will result in different versions of third\-party code being used if \fBany\fR of the gems in the Gemfile(5) or any of their dependencies have been updated\.
 .
 .SH "CONSERVATIVE UPDATING"
 When you make a change to the Gemfile(5) and then run \fBbundle install\fR, Bundler will update only the gems that you modified\.

data/man/bundle-install.1.txt

@@ -289,22 +289,12 @@ THE GEMFILE.LOCK
        gem in your Gemfile(5)) can result in radically	different  gems  being
        needed to satisfy all dependencies.
 
-       As  a  result, you SHOULD check your Gemfile.lock into version control,
-       in both applications and gems. If you do not, every machine that checks
-       out your repository (including your production server) will resolve all
-       dependencies  again,  which  will  result  in  different  versions   of
-       third-party code being used if any of the gems in the Gemfile(5) or any
-       of their dependencies have been updated.
-
-       When Bundler first shipped, the Gemfile.lock was included in the  .git-
-       ignore file included with generated gems. Over time, however, it became
-       clear that this practice forces the pain of  broken  dependencies  onto
-       new  contributors,  while  leaving  existing  contributors  potentially
-       unaware of the problem. Since bundle install is usually the first  step
-       towards	a contribution, the pain of broken dependencies would discour-
-       age new contributors from contributing. As a result,  we  have  revised
-       our  guidance for gem authors to now recommend checking in the lock for
-       gems.
+       As  a  result, you SHOULD check your Gemfile.lock into version control.
+       If you do not, every machine that checks out your repository (including
+       your production server) will resolve all dependencies again, which will
+       result in different versions of third-party code being used if  any  of
+       the  gems  in  the  Gemfile(5)  or  any of their dependencies have been
+       updated.
 
 CONSERVATIVE UPDATING
        When you make a change to the Gemfile(5) and then run  bundle  install,
@@ -392,4 +382,4 @@ SEE ALSO
 
 
 
-				 October 2018		     BUNDLE-INSTALL(1)
+				September 2018		     BUNDLE-INSTALL(1)

data/man/bundle-install.ronn

@@ -290,21 +290,12 @@ of a dependency of a gem in your Gemfile(5)) can result in radically
 different gems being needed to satisfy all dependencies.
 
 As a result, you `SHOULD` check your `Gemfile.lock` into version
-control, in both applications and gems. If you do not, every machine that
-checks out your repository (including your production server) will resolve all
+control. If you do not, every machine that checks out your
+repository (including your production server) will resolve all
 dependencies again, which will result in different versions of
 third-party code being used if `any` of the gems in the Gemfile(5)
 or any of their dependencies have been updated.
 
-When Bundler first shipped, the `Gemfile.lock` was included in the `.gitignore`
-file included with generated gems.  Over time, however, it became clear that
-this practice forces the pain of broken dependencies onto new contributors,
-while leaving existing contributors potentially unaware of the problem. Since
-`bundle install` is usually the first step towards a contribution, the pain of
-broken dependencies would discourage new contributors from contributing. As a
-result, we have revised our guidance for gem authors to now recommend checking
-in the lock for gems.
-
 ## CONSERVATIVE UPDATING
 
 When you make a change to the Gemfile(5) and then run `bundle install`,

data/man/bundle-list.1

@@ -1,20 +1,50 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LIST" "1" "October 2018" "" ""
+.TH "BUNDLE\-LIST" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle
 .
 .SH "SYNOPSIS"
-\fBbundle list\fR [\-\-name\-only]
+\fBbundle list\fR [\-\-name\-only] [\-\-paths] [\-\-without\-group=GROUP] [\-\-only\-group=GROUP]
 .
 .SH "DESCRIPTION"
 Prints a list of all the gems in the bundle including their version\.
 .
+.P
+Example:
+.
+.P
+bundle list \-\-name\-only
+.
+.P
+bundle list \-\-paths
+.
+.P
+bundle list \-\-without\-group test
+.
+.P
+bundle list \-\-only\-group dev
+.
+.P
+bundle list \-\-only\-group dev \-\-paths
+.
 .SH "OPTIONS"
 .
 .TP
 \fB\-\-name\-only\fR
 Print only the name of each gem\.
+.
+.TP
+\fB\-\-paths\fR
+Print the path to each gem in the bundle\.
+.
+.TP
+\fB\-\-without\-group\fR
+Print all gems expect from a group\.
+.
+.TP
+\fB\-\-only\-group\fR
+Print gems from a particular group\.
 

data/man/bundle-list.1.txt

@@ -6,16 +6,38 @@ NAME
        bundle-list - List all the gems in the bundle
 
 SYNOPSIS
-       bundle list [--name-only]
+       bundle	 list	 [--name-only]	  [--paths]    [--without-group=GROUP]
+       [--only-group=GROUP]
 
 DESCRIPTION
        Prints a list of all the gems in the bundle including their version.
 
+       Example:
+
+       bundle list --name-only
+
+       bundle list --paths
+
+       bundle list --without-group test
+
+       bundle list --only-group dev
+
+       bundle list --only-group dev --paths
+
 OPTIONS
        --name-only
 	      Print only the name of each gem.
 
+       --paths
+	      Print the path to each gem in the bundle.
+
+       --without-group
+	      Print all gems expect from a group.
+
+       --only-group
+	      Print gems from a particular group.
+
 
 
 
-				 October 2018			BUNDLE-LIST(1)
+				September 2018			BUNDLE-LIST(1)

data/man/bundle-list.ronn

@@ -3,13 +3,31 @@ bundle-list(1) -- List all the gems in the bundle
 
 ## SYNOPSIS
 
-`bundle list` [--name-only]
+`bundle list` [--name-only] [--paths] [--without-group=GROUP] [--only-group=GROUP]
 
 ## DESCRIPTION
 
 Prints a list of all the gems in the bundle including their version.
 
+Example:
+
+bundle list --name-only
+
+bundle list --paths
+
+bundle list --without-group test
+
+bundle list --only-group dev
+
+bundle list --only-group dev --paths
+
 ## OPTIONS
 
 * `--name-only`:
   Print only the name of each gem.
+* `--paths`:
+  Print the path to each gem in the bundle.
+* `--without-group`:
+  Print all gems expect from a group.
+* `--only-group`:
+  Print gems from a particular group.

data/man/bundle-lock.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LOCK" "1" "October 2018" "" ""
+.TH "BUNDLE\-LOCK" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing

data/man/bundle-lock.1.txt

@@ -90,4 +90,4 @@ PATCH LEVEL OPTIONS
 
 
 
-				 October 2018			BUNDLE-LOCK(1)
+				September 2018			BUNDLE-LOCK(1)

data/man/bundle-open.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OPEN" "1" "October 2018" "" ""
+.TH "BUNDLE\-OPEN" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-open\fR \- Opens the source directory for a gem in your bundle

data/man/bundle-open.1.txt

@@ -26,4 +26,4 @@ DESCRIPTION
 
 
 
-				 October 2018			BUNDLE-OPEN(1)
+				September 2018			BUNDLE-OPEN(1)

data/man/bundle-outdated.1

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "October 2018" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available
 .
 .SH "SYNOPSIS"
-\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-update\-strict] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch]
+\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-update\-strict] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch] [\-\-only\-explicit]
 .
 .SH "DESCRIPTION"
 Outdated lists the names and versions of gems that have a newer version available in the given source\. Calling outdated with [GEM [GEM]] will only check for newer versions of the given gems\. Prerelease gems are ignored by default\. If your gems are up to date, Bundler will exit with a status of 0\. Otherwise, it will exit 1\.
@@ -70,6 +70,10 @@ Only list minor newer versions\.
 \fB\-\-filter\-patch\fR
 Only list patch newer versions\.
 .
+.TP
+\fB\-\-only\-explicit\fR
+Only list gems specified in your Gemfile, not their dependencies\.
+.
 .SH "PATCH LEVEL OPTIONS"
 See bundle update(1) \fIbundle\-update\.1\.html\fR for details\.
 .

data/man/bundle-outdated.1.txt

@@ -9,7 +9,7 @@ SYNOPSIS
        bundle	outdated   [GEM]   [--local]   [--pre]	[--source]  [--strict]
        [--parseable	|     --porcelain]     [--group=GROUP]	    [--groups]
        [--update-strict]  [--patch|--minor|--major]  [--filter-major]  [--fil-
-       ter-minor] [--filter-patch]
+       ter-minor] [--filter-patch] [--only-explicit]
 
 DESCRIPTION
        Outdated lists the names and versions of gems that have a newer version
@@ -62,17 +62,21 @@ OPTIONS
        --filter-patch
 	      Only list patch newer versions.
 
+       --only-explicit
+	      Only list gems specified in your Gemfile,  not  their  dependen-
+	      cies.
+
 PATCH LEVEL OPTIONS
        See bundle update(1) bundle-update.1.html for details.
 
-       One difference between the patch level options  in  bundle  update  and
+       One  difference	between  the  patch level options in bundle update and
        here is the --strict option. --strict was already an option on outdated
        before the patch level options were added. --strict wasn't altered, and
-       the  --update-strict  option on outdated reflects what --strict does on
+       the --update-strict option on outdated reflects what --strict  does  on
        bundle update.
 
 FILTERING OUTPUT
-       The 3 filtering options do  not	affect	the  resolution  of  versions,
+       The  3  filtering  options  do  not  affect the resolution of versions,
        merely what versions are shown in the output.
 
        If the regular output shows the following:
@@ -119,9 +123,9 @@ FILTERING OUTPUT
 
 
 
-       Combining all three filter options would be the same result as  provid-
+       Combining  all three filter options would be the same result as provid-
        ing none of them.
 
 
 
-				 October 2018		    BUNDLE-OUTDATED(1)
+				September 2018		    BUNDLE-OUTDATED(1)

data/man/bundle-outdated.ronn

@@ -15,6 +15,7 @@ bundle-outdated(1) -- List installed gems with newer versions available
                         [--filter-major]
                         [--filter-minor]
                         [--filter-patch]
+                        [--only-explicit]
 
 ## DESCRIPTION
 
@@ -67,6 +68,9 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
 * `--filter-patch`:
   Only list patch newer versions.
 
+* `--only-explicit`:
+  Only list gems specified in your Gemfile, not their dependencies.
+
 ## PATCH LEVEL OPTIONS
 
 See [bundle update(1)](bundle-update.1.html) for details.