bundler 1.16.1 → 1.17.3

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" "February 2017" "" ""
+.TH "BUNDLE\-INFO" "1" "November 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
 
 
 
-				 February 2017			BUNDLE-INFO(1)
+				 November 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" "February 2017" "" ""
+.TH "BUNDLE\-INIT" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-init\fR \- Generates a Gemfile into the current working directory
@@ -10,11 +10,16 @@
 \fBbundle init\fR [\-\-gemspec=FILE]
 .
 .SH "DESCRIPTION"
-Init generates a default \fBGemfile(5)\fR in the current working directory\. When adding a \fBGemfile(5)\fR to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created \fBGemfile(5)\fR\.
+Init generates a default [\fBGemfile(5)\fR][Gemfile(5)] in the current working directory\. When adding a [\fBGemfile(5)\fR][Gemfile(5)] to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .SH "OPTIONS"
 .
 .TP
 \fB\-\-gemspec\fR
-Use the specified \.gemspec to create the \fBGemfile(5)\fR
-
+Use the specified \.gemspec to create the [\fBGemfile(5)\fR][Gemfile(5)]
+.
+.SH "FILES"
+Included in the default [\fBGemfile(5)\fR][Gemfile(5)] generated is the line \fB# frozen_string_literal: true\fR\. This is a magic comment supported for the first time in Ruby 2\.3\. The presence of this line results in all string literals in the file being implicitly frozen\.
+.
+.SH "SEE ALSO"
+Gemfile(5) \fIhttp://bundler\.io/man/gemfile\.5\.html\fR

data/man/bundle-init.1.txt

@@ -9,16 +9,26 @@ SYNOPSIS
        bundle init [--gemspec=FILE]
 
 DESCRIPTION
-       Init  generates	a default Gemfile(5) in the current working directory.
-       When adding a Gemfile(5) to a gem with a gemspec, the --gemspec	option
-       will  automatically  add  each dependency listed in the gemspec file to
-       the newly created Gemfile(5).
+       Init  generates a default [Gemfile(5)][Gemfile(5)] in the current work-
+       ing directory. When adding a [Gemfile(5)][Gemfile(5)] to a gem  with  a
+       gemspec,  the  --gemspec  option will automatically add each dependency
+       listed in the gemspec  file  to	the  newly  created  [Gemfile(5)][Gem-
+       file(5)].
 
 OPTIONS
        --gemspec
-	      Use the specified .gemspec to create the Gemfile(5)
+	      Use  the	specified  .gemspec  to  create  the [Gemfile(5)][Gem-
+	      file(5)]
 
+FILES
+       Included in the default [Gemfile(5)][Gemfile(5)] generated is the  line
+       #  frozen_string_literal:  true.  This is a magic comment supported for
+       the first time in Ruby 2.3. The presence of this line  results  in  all
+       string literals in the file being implicitly frozen.
 
+SEE ALSO
+       Gemfile(5) http://bundler.io/man/gemfile.5.html
 
 
-				 February 2017			BUNDLE-INIT(1)
+
+				 November 2018			BUNDLE-INIT(1)

data/man/bundle-init.ronn

@@ -7,12 +7,23 @@ bundle-init(1) -- Generates a Gemfile into the current working directory
 
 ## DESCRIPTION
 
-Init generates a default `Gemfile(5)` in the current working directory. When
-adding a `Gemfile(5)` to a gem with a gemspec, the `--gemspec` option will
+Init generates a default [`Gemfile(5)`][Gemfile(5)] in the current working directory. When
+adding a [`Gemfile(5)`][Gemfile(5)] to a gem with a gemspec, the `--gemspec` option will
 automatically add each dependency listed in the gemspec file to the newly
-created `Gemfile(5)`.
+created [`Gemfile(5)`][Gemfile(5)].
 
 ## OPTIONS
 
 * `--gemspec`:
-  Use the specified .gemspec to create the `Gemfile(5)`
+  Use the specified .gemspec to create the [`Gemfile(5)`][Gemfile(5)]
+
+## FILES
+
+Included in the default [`Gemfile(5)`][Gemfile(5)]
+generated is the line `# frozen_string_literal: true`. This is a magic comment
+supported for the first time in Ruby 2.3. The presence of this line
+results in all string literals in the file being implicitly frozen.
+
+## SEE ALSO
+
+[Gemfile(5)](http://bundler.io/man/gemfile.5.html)

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" "February 2017" "" ""
+.TH "BUNDLE\-INJECT" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile
@@ -10,10 +10,10 @@
 \fBbundle inject\fR [GEM] [VERSION]
 .
 .SH "DESCRIPTION"
-Adds the named gem(s) with their version requirements to the resolved \fBGemfile(5)\fR\.
+Adds the named gem(s) with their version requirements to the resolved [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .P
-This command will add the gem to both your \fBGemfile(5)\fR and Gemfile\.lock if it isn\'t listed yet\.
+This command will add the gem to both your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock if it isn\'t listed yet\.
 .
 .P
 Example:
@@ -30,4 +30,4 @@ bundle inject \'rack\' \'> 0\'
 .IP "" 0
 .
 .P
-This will inject the \'rack\' gem with a version greater than 0 in your \fBGemfile(5)\fR and Gemfile\.lock
+This will inject the \'rack\' gem with a version greater than 0 in your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock

data/man/bundle-inject.1.txt

@@ -10,10 +10,10 @@ SYNOPSIS
 
 DESCRIPTION
        Adds  the  named gem(s) with their version requirements to the resolved
-       Gemfile(5).
+       [Gemfile(5)][Gemfile(5)].
 
-       This command will add the gem to both your Gemfile(5) and  Gemfile.lock
-       if it isn't listed yet.
+       This command will add the gem to both your [Gemfile(5)][Gemfile(5)] and
+       Gemfile.lock if it isn't listed yet.
 
        Example:
 
@@ -25,8 +25,8 @@ DESCRIPTION
 
 
        This  will  inject the 'rack' gem with a version greater than 0 in your
-       Gemfile(5) and Gemfile.lock
+       [Gemfile(5)][Gemfile(5)] and Gemfile.lock
 
 
 
-				 February 2017		      BUNDLE-INJECT(1)
+				 November 2018		      BUNDLE-INJECT(1)

data/man/bundle-inject.ronn

@@ -8,9 +8,9 @@ bundle-inject(1) -- Add named gem(s) with version requirements to Gemfile
 ## DESCRIPTION
 
 Adds the named gem(s) with their version requirements to the resolved
-`Gemfile(5)`.
+[`Gemfile(5)`][Gemfile(5)].
 
-This command will add the gem to both your `Gemfile(5)` and Gemfile.lock if it
+This command will add the gem to both your [`Gemfile(5)`][Gemfile(5)] and Gemfile.lock if it
 isn't listed yet.
 
 Example:
@@ -19,4 +19,4 @@ Example:
     bundle inject 'rack' '> 0'
 
 This will inject the 'rack' gem with a version greater than 0 in your
-`Gemfile(5)` and Gemfile.lock
+[`Gemfile(5)`][Gemfile(5)] and Gemfile.lock

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" "December 2017" "" ""
+.TH "BUNDLE\-INSTALL" "1" "December 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-install\fR \- Install the dependencies specified in your Gemfile
@@ -35,7 +35,7 @@ In \fIdeployment mode\fR, Bundler will \'roll\-out\' the bundle for production o
 .
 .TP
 \fB\-\-force\fR
-Force download every gem, even if the required versions are already available locally\.
+Force download every gem, even if the required versions are already available locally\. \fB\-\-redownload\fR is an alias of this option\.
 .
 .TP
 \fB\-\-frozen\fR
@@ -221,7 +221,10 @@ 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\. 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\.
+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\.
 .
 .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\.
@@ -291,7 +294,7 @@ Even though \fBactivemerchant\fR declares a very loose dependency that theoretic
 To explicitly update \fBactionpack\fR, including its dependencies which other gems in the Gemfile(5) still depend on, run \fBbundle update actionpack\fR (see \fBbundle update(1)\fR)\.
 .
 .P
-\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, which will guarantee that no other gem in the Gemfile(5) is impacted by the change\. If that does not work, run [bundle update(1)][bundle\-update]\.
+\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, which will guarantee that no other gem in the Gemfile(5) is impacted by the change\. If that does not work, run bundle update(1) \fIbundle\-update\.1\.html\fR\.
 .
 .SH "SEE ALSO"
 .