bundler 1.16.0 → 1.16.1

data/man/bundle-list.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LIST" "1" "October 2017" "" ""
+.TH "BUNDLE\-LIST" "1" "August 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle

data/man/bundle-list.1.txt

@@ -2,20 +2,20 @@ BUNDLE-LIST(1)							BUNDLE-LIST(1)
 
 
 
-1mNAME0m
-       1mbundle-list 22m- List all the gems in the bundle
+NAME
+       bundle-list - List all the gems in the bundle
 
-1mSYNOPSIS0m
-       1mbundle list 22m[--name-only]
+SYNOPSIS
+       bundle list [--name-only]
 
-1mDESCRIPTION0m
+DESCRIPTION
        Prints a list of all the gems in the bundle including their version.
 
-1mOPTIONS0m
-       1m--name-only0m
+OPTIONS
+       --name-only
 	      Print only the name of each gem.
 
 
 
 
-				 October 2017			BUNDLE-LIST(1)
+				  August 2017			BUNDLE-LIST(1)

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" "September 2017" "" ""
+.TH "BUNDLE\-LOCK" "1" "February 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing

data/man/bundle-lock.1.txt

@@ -2,92 +2,92 @@ BUNDLE-LOCK(1)							BUNDLE-LOCK(1)
 
 
 
-1mNAME0m
-       1mbundle-lock 22m- Creates / Updates a lockfile without installing
+NAME
+       bundle-lock - Creates / Updates a lockfile without installing
 
-1mSYNOPSIS0m
-       1mbundle    lock   22m[--update]   [--local]   [--print]   [--lockfile=PATH]
+SYNOPSIS
+       bundle	 lock	[--update]   [--local]	 [--print]   [--lockfile=PATH]
        [--full-index] [--add-platform] [--remove-platform] [--patch] [--minor]
        [--major] [--strict] [--conservative]
 
-1mDESCRIPTION0m
+DESCRIPTION
        Lock the gems specified in Gemfile.
 
-1mOPTIONS0m
-       1m--update=<*gems>0m
+OPTIONS
+       --update=<*gems>
 	      Ignores  the  existing  lockfile. Resolve then updates lockfile.
-	      Taking a list of gems or updating all gems if no list is given.
+	      Taking a list of gems or updating all gems if no list is	given.
 
-       1m--local0m
-	      Do not attempt to connect to 1mrubygems.org22m. Instead, Bundler will
-	      use  the	gems  already  present	in  Rubygems' cache or in 1mven-0m
-	      1mdor/cache22m. Note that  if  a	appropriate  platform-specific	gem
-	      exists on 1mrubygems.org 22mit will not be found.
+       --local
+	      Do not attempt to connect to rubygems.org. Instead, Bundler will
+	      use the gems already present  in	Rubygems'  cache  or  in  ven-
+	      dor/cache.  Note	that  if  a  appropriate platform-specific gem
+	      exists on rubygems.org it will not be found.
 
-       1m--print0m
-	      Prints  the  lockfile  to  STDOUT instead of writing to the file
+       --print
+	      Prints the lockfile to STDOUT instead of	writing  to  the  file
 	      system.
 
-       1m--lockfile=<path>0m
+       --lockfile=<path>
 	      The path where the lockfile should be written to.
 
-       1m--full-index0m
+       --full-index
 	      Fall back to using the single-file index of all gems.
 
-       1m--add-platform0m
-	      Add a new platform to the lockfile, re-resolving for  the  addi-
+       --add-platform
+	      Add  a  new platform to the lockfile, re-resolving for the addi-
 	      tion of that platform.
 
-       1m--remove-platform0m
+       --remove-platform
 	      Remove a platform from the lockfile.
 
-       1m--patch0m
+       --patch
 	      If updating, prefer updating only to next patch version.
 
-       1m--minor0m
+       --minor
 	      If updating, prefer updating only to next minor version.
 
-       1m--major0m
+       --major
 	      If updating, prefer updating to next major version (default).
 
-       1m--strict0m
-	      If  updating,  do  not  allow  any gem to be updated past latest
+       --strict
+	      If updating, do not allow any gem  to  be  updated  past	latest
 	      --patch | --minor | --major.
 
-       1m--conservative0m
+       --conservative
 	      If updating, use bundle install conservative update behavior and
 	      do not allow shared dependencies to be updated.
 
-1mUPDATING ALL GEMS0m
-       If  you	run  1mbundle  lock  22mwith  1m--update 22moption without list of gems,
-       bundler will ignore any	previously  installed  gems  and  resolve  all
-       dependencies  again  based on the latest versions of all gems available
+UPDATING ALL GEMS
+       If you run bundle lock with  --update  option  without  list  of  gems,
+       bundler	will  ignore  any  previously  installed  gems and resolve all
+       dependencies again based on the latest versions of all  gems  available
        in the sources.
 
-1mUPDATING A LIST OF GEMS0m
+UPDATING A LIST OF GEMS
        Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the  rest  of the gems that you specified locked to the versions in the
-       1mGemfile.lock22m.
+       the rest of the gems that you specified locked to the versions  in  the
+       Gemfile.lock.
 
-       For instance, you  only	want  to  update  1mnokogiri22m,  run  1mbundle  lock0m
-       1m--update nokogiri22m.
+       For  instance,  you  only  want	to  update  nokogiri,  run bundle lock
+       --update nokogiri.
 
-       Bundler will update 1mnokogiri 22mand any of its dependencies, but leave the
-       rest of the gems that you specified locked to the versions in the  1mGem-0m
-       1mfile.lock22m.
+       Bundler will update nokogiri and any of its dependencies, but leave the
+       rest  of the gems that you specified locked to the versions in the Gem-
+       file.lock.
 
-1mSUPPORTING OTHER PLATFORMS0m
-       If  you want your bundle to support platforms other than the one you're
-       running locally, you can run 1mbundle lock --add-platform PLATFORM 22mto add
-       PLATFORM  to the lockfile, force bundler to re-resolve and consider the
-       new platform when picking gems, all without needing to have  a  machine
+SUPPORTING OTHER PLATFORMS
+       If you want your bundle to support platforms other than the one	you're
+       running locally, you can run bundle lock --add-platform PLATFORM to add
+       PLATFORM to the lockfile, force bundler to re-resolve and consider  the
+       new  platform  when picking gems, all without needing to have a machine
        that matches PLATFORM handy to install those platform-specific gems on.
 
-       For a full explanation of gem platforms, see 1mgem help platform22m.
+       For a full explanation of gem platforms, see gem help platform.
 
-1mPATCH LEVEL OPTIONS0m
+PATCH LEVEL OPTIONS
        See [bundle update(1)][bundle-update] for details.
 
 
 
-				September 2017			BUNDLE-LOCK(1)
+				 February 2017			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" "September 2017" "" ""
+.TH "BUNDLE\-OPEN" "1" "February 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-open\fR \- Opens the source directory for a gem in your bundle

data/man/bundle-open.1.txt

@@ -2,16 +2,16 @@ BUNDLE-OPEN(1)							BUNDLE-OPEN(1)
 
 
 
-1mNAME0m
-       1mbundle-open 22m- Opens the source directory for a gem in your bundle
+NAME
+       bundle-open - Opens the source directory for a gem in your bundle
 
-1mSYNOPSIS0m
-       1mbundle open 22m[GEM]
+SYNOPSIS
+       bundle open [GEM]
 
-1mDESCRIPTION0m
+DESCRIPTION
        Opens the source directory of the provided GEM in your editor.
 
-       For  this to work the 1mEDITOR 22mor 1mBUNDLER_EDITOR 22menvironment variable has
+       For  this to work the EDITOR or BUNDLER_EDITOR environment variable has
        to be set.
 
        Example:
@@ -26,4 +26,4 @@ BUNDLE-OPEN(1)							BUNDLE-OPEN(1)
 
 
 
-				September 2017			BUNDLE-OPEN(1)
+				 February 2017			BUNDLE-OPEN(1)

data/man/bundle-outdated.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "October 2017" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "July 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available

data/man/bundle-outdated.1.txt

@@ -2,76 +2,76 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-1mNAME0m
-       1mbundle-outdated 22m- List installed gems with newer versions available
+NAME
+       bundle-outdated - List installed gems with newer versions available
 
-1mSYNOPSIS0m
-       1mbundle   outdated   22m[GEM]	[--local]   [--pre]  [--source]  [--strict]
+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]
 
-1mDESCRIPTION0m
+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.
 
-1mOPTIONS0m
-       1m--local0m
+OPTIONS
+       --local
 	      Do not attempt to fetch gems remotely  and  use  the  gem  cache
 	      instead.
 
-       1m--pre	22mCheck for newer pre-release gems.
+       --pre  Check for newer pre-release gems.
 
-       1m--source0m
+       --source
 	      Check against a specific source.
 
-       1m--strict0m
+       --strict
 	      Only list newer versions allowed by your Gemfile requirements.
 
-       1m--parseable22m, 1m--porcelain0m
+       --parseable, --porcelain
 	      Use minimal formatting for more parseable output.
 
-       1m--group0m
+       --group
 	      List gems from a specific group.
 
-       1m--groups0m
+       --groups
 	      List gems organized by groups.
 
-       1m--update-strict0m
+       --update-strict
 	      Strict  conservative  resolution,  do  not  allow  any gem to be
 	      updated past latest --patch | --minor| --major.
 
-       1m--minor0m
+       --minor
 	      Prefer updating only to next minor version.
 
-       1m--major0m
+       --major
 	      Prefer updating to next major version (default).
 
-       1m--patch0m
+       --patch
 	      Prefer updating only to next patch version.
 
-       1m--filter-major0m
+       --filter-major
 	      Only list major newer versions.
 
-       1m--filter-minor0m
+       --filter-minor
 	      Only list minor newer versions.
 
-       1m--filter-patch0m
+       --filter-patch
 	      Only list patch newer versions.
 
-1mPATCH LEVEL OPTIONS0m
+PATCH LEVEL OPTIONS
        See [bundle update(1)][bundle-update] for details.
 
-       One difference between the patch level options  in  1mbundle  update  22mand
-       here is the 1m--strict 22moption. 1m--strict 22mwas already an option on outdated
-       before the patch level options were added. 1m--strict 22mwasn't altered, and
-       the  1m--update-strict  22moption on 1moutdated 22mreflects what 1m--strict 22mdoes on
-       1mbundle update22m.
+       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
+       bundle update.
 
-1mFILTERING OUTPUT0m
+FILTERING OUTPUT
        The 3 filtering options do  not	affect	the  resolution  of  versions,
        merely what versions are shown in the output.
 
@@ -85,7 +85,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       1m--filter-major 22mwould only show:
+       --filter-major would only show:
 
 
 
@@ -93,7 +93,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       1m--filter-minor 22mwould only show:
+       --filter-minor would only show:
 
 
 
@@ -101,7 +101,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       1m--filter-patch 22mwould only show:
+       --filter-patch would only show:
 
 
 
@@ -109,7 +109,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       Filter options can be combined. 1m--filter-minor 22mand 1m--filter-patch 22mwould
+       Filter options can be combined. --filter-minor and --filter-patch would
        show:
 
 
@@ -119,9 +119,9 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       Combining all three 1mfilter 22moptions would be the same result as  provid-
+       Combining all three filter options would be the same result as  provid-
        ing none of them.
 
 
 
-				 October 2017		    BUNDLE-OUTDATED(1)
+				   July 2017		    BUNDLE-OUTDATED(1)

data/man/bundle-package.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PACKAGE" "1" "October 2017" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "September 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application

data/man/bundle-package.1.txt

@@ -2,36 +2,36 @@ BUNDLE-PACKAGE(1)					     BUNDLE-PACKAGE(1)
 
 
 
-1mNAME0m
-       1mbundle-package 22m- Package your needed 1m.gem 22mfiles into your application
+NAME
+       bundle-package - Package your needed .gem files into your application
 
-1mSYNOPSIS0m
-       1mbundle package0m
+SYNOPSIS
+       bundle package
 
-1mDESCRIPTION0m
-       Copy  all of the 1m.gem 22mfiles needed to run the application into the 1mven-0m
-       1mdor/cache   22mdirectory.   In   the	future,   when	 running    [bundle
+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 1mrubygems.org22m.
+       the ones on rubygems.org.
 
-1mGIT AND PATH GEMS0m
-       Since Bundler 1.2, the 1mbundle package 22mcommand can also package 1m:git 22mand
-       1m:path	22mdependencies  besides  .gem	files.	This needs to be explicitly
-       enabled via the 1m--all 22moption. Once	used,  the  1m--all  22moption	will  be
+GIT AND PATH GEMS
+       Since Bundler 1.2, the bundle package 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.
 
-1mSUPPORT FOR MULTIPLE PLATFORMS0m
+SUPPORT FOR MULTIPLE PLATFORMS
        When  using  gems that have different packages for different platforms,
        Bundler 1.8 and newer support caching of gems for other platforms where
-       the  Gemfile  has  been resolved (i.e. present in the lockfile) in 1mven-0m
-       1mdor/cache22m. This needs to be enabled  via  the  1m--all-platforms  22moption.
+       the  Gemfile  has  been resolved (i.e. present in the lockfile) in ven-
+       dor/cache. This needs to be enabled  via  the  --all-platforms  option.
        This setting will be remembered in your local bundler configuration.
 
-1mREMOTE FETCHING0m
+REMOTE FETCHING
        By  default,  if you run [bundle install(1)][bundle-install] after run-
        ning [bundle package(1)][bundle-package], bundler will still connect to
-       1mrubygems.org 22mto check whether a platform-specific gem exists for any of
-       the gems in 1mvendor/cache22m.
+       rubygems.org to check whether a platform-specific gem exists for any of
+       the gems in vendor/cache.
 
        For instance, consider this Gemfile(5):
 
@@ -43,37 +43,37 @@ BUNDLE-PACKAGE(1)					     BUNDLE-PACKAGE(1)
 
 
 
-       If you run 1mbundle package 22munder C Ruby, bundler will retrieve the  ver-
-       sion  of  1mnokogiri  22mfor the 1m"ruby" 22mplatform. If you deploy to JRuby and
-       run 1mbundle install22m, bundler is forced to check to see whether a  1m"java"0m
-       platformed 1mnokogiri 22mexists.
+       If you run bundle package under C Ruby, bundler will retrieve the  ver-
+       sion  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  1mnokogiri  22mgem  for  the Ruby platform is 4mtechnically0m
+       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 1mrubygems.org 22mto
+       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 1m"java" 22mplatform. A similar
+       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 1mvendor/cache 22mare appro-
-       priate for the platform you are on, you can run 1mbundle install  --local0m
-       to  skip  checking  for more appropriate gems, and use the ones in 1mven-0m
-       1mdor/cache22m.
+       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 1mbundle package 22mon an identical machine and check in
-       the gems. For instance, you can run  1mbundle  package  22mon  an  identical
-       staging	box during your staging process, and check in the 1mvendor/cache0m
+       your gems is to run bundle package on an identical machine and check in
+       the gems. For instance, you can run  bundle  package  on  an  identical
+       staging	box during your staging process, and check in the vendor/cache
        before deploying to production.
 
        By  default,  [bundle  package(1)][bundle-package]  fetches  and   also
        installs  the gems to the default location. To package the dependencies
-       to 1mvendor/cache 22mwithout installing them to the local install  location,
-       you can run 1mbundle package --no-install22m.
+       to vendor/cache without installing them to the local install  location,
+       you can run bundle package --no-install.
 
 
 
-				 October 2017		     BUNDLE-PACKAGE(1)
+				September 2017		     BUNDLE-PACKAGE(1)