bundler 1.15.1 → 1.17.3

data/man/bundle-outdated.1.txt

@@ -2,77 +2,81 @@ 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]
+       ter-minor] [--filter-patch] [--only-explicit]
 
-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--parseable0m
+       --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
-       See bundle update(1) 4mbundle-update.1.html24m for details.
+       --only-explicit
+	      Only list gems specified in your Gemfile,  not  their  dependen-
+	      cies.
 
-       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.
+PATCH LEVEL OPTIONS
+       See bundle update(1) bundle-update.1.html for details.
 
-1mFILTERING OUTPUT0m
-       The 3 filtering options do  not	affect	the  resolution  of  versions,
+       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.
+
+FILTERING OUTPUT
+       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:
@@ -85,7 +89,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       1m--filter-major 22mwould only show:
+       --filter-major would only show:
 
 
 
@@ -93,7 +97,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       1m--filter-minor 22mwould only show:
+       --filter-minor would only show:
 
 
 
@@ -101,7 +105,7 @@ BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
 
 
 
-       1m--filter-patch 22mwould only show:
+       --filter-patch would only show:
 
 
 
@@ -109,7 +113,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 +123,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.
 
 
 
-				   May 2017		    BUNDLE-OUTDATED(1)
+				 December 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
 
@@ -37,7 +38,7 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
 * `--strict`:
   Only list newer versions allowed by your Gemfile requirements.
 
-* `--parseable`:
+* `--parseable`, `--porcelain`:
    Use minimal formatting for more parseable output.
 
 * `--group`:
@@ -67,9 +68,12 @@ 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] for details.
+See [bundle update(1)](bundle-update.1.html) for details.
 
 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`

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" "January 2017" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
@@ -10,7 +10,7 @@
 \fBbundle package\fR
 .
 .SH "DESCRIPTION"
-Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running bundle install(1) \fIbundle\-install\.1\.html\fR, use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
+Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
 .
 .SH "GIT AND PATH GEMS"
 Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
@@ -19,7 +19,7 @@ Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR
 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 \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
 .
 .SH "REMOTE FETCHING"
-By default, if you run bundle install(1) \fIbundle\-install\.1\.html\fR after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
+By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
 .
 .P
 For instance, consider this Gemfile(5):
@@ -50,3 +50,6 @@ If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriat
 .
 .P
 One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
+.
+.P
+By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.

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
-
-1mSYNOPSIS0m
-       1mbundle package0m
-
-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 install(1) 4mbun-0m
-       4mdle-install.1.html24m, use the gems in the cache in preference to the ones
-       on 1mrubygems.org22m.
-
-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
+NAME
+       bundle-package - Package your needed .gem files into your application
+
+SYNOPSIS
+       bundle package
+
+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
+       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
-       By  default,  if  you run bundle install(1) 4mbundle-install.1.html24m after
-       running bundle package(1)  4mbundle-package.1.html24m,  bundler	will  still
-       connect to 1mrubygems.org 22mto check whether a platform-specific gem exists
-       for any of the gems in 1mvendor/cache22m.
+REMOTE FETCHING
+       By  default, if you run bundle install(1)](bundle-install.1.html) after
+       running bundle package(1)  bundle-package.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):
 
@@ -43,32 +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.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 package --no-install.
 
 
-				 January 2017		     BUNDLE-PACKAGE(1)
+
+				 November 2018		     BUNDLE-PACKAGE(1)

data/man/bundle-package.ronn

@@ -27,8 +27,8 @@ in your local bundler configuration.
 
 ## REMOTE FETCHING
 
-By default, if you run [bundle install(1)][bundle-install] after running
-[bundle package(1)][bundle-package], bundler will still connect to `rubygems.org`
+By default, if you run `bundle install(1)`](bundle-install.1.html) after running
+[bundle package(1)](bundle-package.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`.
 
@@ -65,3 +65,8 @@ 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.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 package --no-install`.

data/man/bundle-platform.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PLATFORM" "1" "January 2017" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -2,14 +2,14 @@ BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
 
 
 
-1mNAME0m
-       1mbundle-platform 22m- Displays platform compatibility information
+NAME
+       bundle-platform - Displays platform compatibility information
 
-1mSYNOPSIS0m
-       1mbundle platform 22m[--ruby]
+SYNOPSIS
+       bundle platform [--ruby]
 
-1mDESCRIPTION0m
-       1mplatform  22mwill display information from your Gemfile, Gemfile.lock, and
+DESCRIPTION
+       platform  will display information from your Gemfile, Gemfile.lock, and
        Ruby VM about your platform.
 
        For instance, using this Gemfile(5):
@@ -24,7 +24,7 @@ BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
 
 
 
-       If you run 1mbundle platform 22mon Ruby 1.9.3, it will display the following
+       If you run bundle platform on Ruby 1.9.3, it will display the following
        output:
 
 
@@ -41,17 +41,17 @@ BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
 
 
 
-       1mplatform  22mwill  list  all the platforms in your 1mGemfile.lock 22mas well as
-       the 1mruby 22mdirective if applicable from your Gemfile(5). It will also let
-       you know if the 1mruby 22mdirective requirement has been met. If 1mruby 22mdirec-
+       platform  will  list  all the platforms in your Gemfile.lock as well as
+       the ruby directive if applicable from your Gemfile(5). It will also let
+       you know if the ruby directive requirement has been met. If ruby direc-
        tive doesn't match the running Ruby VM, it will tell you what part does
        not.
 
-1mOPTIONS0m
-       1m--ruby 22mIt  will  display  the  ruby directive information, so you don't
+OPTIONS
+       --ruby It  will	display  the  ruby directive information, so you don't
 	      have to parse it from the Gemfile(5).
 
 
 
 
-				 January 2017		    BUNDLE-PLATFORM(1)
+				 November 2018		    BUNDLE-PLATFORM(1)

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" "May 2017" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition
@@ -10,7 +10,25 @@
 \fBbundle pristine\fR
 .
 .SH "DESCRIPTION"
-\fBpristine\fR restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems\. For git gems \- a forced checkout will be performed\.
+\fBpristine\fR restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems\. For git gems, a forced checkout will be performed\.
 .
 .P
-Note the Bundler gem cannot be restored to its original state with \fBpristine\fR\.
+For further explanation, \fBbundle pristine\fR ignores unpacked files on disk\. In other words, this command utilizes the local \fB\.gem\fR cache or the gem\'s git repository as if one were installing from scratch\.
+.
+.P
+Note: the Bundler gem cannot be restored to its original state with \fBpristine\fR\. One also cannot use \fBbundle pristine\fR on gems with a \'path\' option in the Gemfile, because bundler has no original copy it can restore from\.
+.
+.P
+When is it practical to use \fBbundle pristine\fR?
+.
+.P
+It comes in handy when a developer is debugging a gem\. \fBbundle pristine\fR is a great way to get rid of experimental changes to a gem that one may not want\.
+.
+.P
+Why use \fBbundle pristine\fR over \fBgem pristine \-\-all\fR?
+.
+.P
+Both commands are very similar\. For context: \fBbundle pristine\fR, without arguments, cleans all gems from the lockfile\. Meanwhile, \fBgem pristine \-\-all\fR cleans all installed gems for that Ruby version\.
+.
+.P
+If a developer forgets which gems in their project they might have been debugging, the Rubygems \fBgem pristine [GEMNAME]\fR command may be inconvenient\. One can avoid waiting for \fBgem pristine \-\-all\fR, and instead run \fBbundle pristine\fR\.

data/man/bundle-pristine.1.txt

@@ -2,20 +2,43 @@ BUNDLE-PRISTINE(1)					    BUNDLE-PRISTINE(1)
 
 
 
-1mNAME0m
-       1mbundle-pristine 22m- Restores installed gems to their pristine condition
+NAME
+       bundle-pristine - Restores installed gems to their pristine condition
 
-1mSYNOPSIS0m
-       1mbundle pristine0m
+SYNOPSIS
+       bundle pristine
 
-1mDESCRIPTION0m
-       1mpristine  22mrestores	the  installed gems in the bundle to their pristine
-       condition using the local gem cache from RubyGems. For  git  gems  -  a
+DESCRIPTION
+       pristine  restores  the	installed gems in the bundle to their pristine
+       condition using the local gem cache from  RubyGems.  For  git  gems,  a
        forced checkout will be performed.
 
-       Note  the  Bundler  gem	cannot	be restored to its original state with
-       1mpristine22m.
+       For  further  explanation,  bundle  pristine  ignores unpacked files on
+       disk. In other words, this command utilizes the local .gem cache or the
+       gem's git repository as if one were installing from scratch.
 
+       Note:  the  Bundler  gem  cannot be restored to its original state with
+       pristine. One also cannot use bundle pristine on  gems  with  a	'path'
+       option  in  the	Gemfile,  because  bundler has no original copy it can
+       restore from.
 
+       When is it practical to use bundle pristine?
 
-				   May 2017		    BUNDLE-PRISTINE(1)
+       It comes in handy when a developer is debugging a gem. bundle  pristine
+       is a great way to get rid of experimental changes to a gem that one may
+       not want.
+
+       Why use bundle pristine over gem pristine --all?
+
+       Both commands are very similar. For context: bundle  pristine,  without
+       arguments,  cleans  all gems from the lockfile. Meanwhile, gem pristine
+       --all cleans all installed gems for that Ruby version.
+
+       If a developer forgets which gems in their project they might have been
+       debugging,  the Rubygems gem pristine [GEMNAME] command may be inconve-
+       nient. One can avoid waiting for gem pristine --all,  and  instead  run
+       bundle pristine.
+
+
+
+				 November 2018		    BUNDLE-PRISTINE(1)

data/man/bundle-pristine.ronn

@@ -7,7 +7,28 @@ bundle-pristine(1) -- Restores installed gems to their pristine condition
 
 ## DESCRIPTION
 
-`pristine` restores the installed gems in the bundle to their pristine condition using the local gem
-cache from RubyGems. For git gems - a forced checkout will be performed.
+`pristine` restores the installed gems in the bundle to their pristine condition
+using the local gem cache from RubyGems. For git gems, a forced checkout will be performed.
 
-Note the Bundler gem cannot be restored to its original state with `pristine`.
+For further explanation, `bundle pristine` ignores unpacked files on disk. In other
+words, this command utilizes the local `.gem` cache or the gem's git repository
+as if one were installing from scratch.
+
+Note: the Bundler gem cannot be restored to its original state with `pristine`.
+One also cannot use `bundle pristine` on gems with a 'path' option in the Gemfile,
+because bundler has no original copy it can restore from.
+
+When is it practical to use `bundle pristine`?
+
+It comes in handy when a developer is debugging a gem. `bundle pristine` is a
+great way to get rid of experimental changes to a gem that one may not want.
+
+Why use `bundle pristine` over `gem pristine --all`?
+
+Both commands are very similar.
+For context: `bundle pristine`, without arguments, cleans all gems from the lockfile.
+Meanwhile, `gem pristine --all` cleans all installed gems for that Ruby version.
+
+If a developer forgets which gems in their project they might
+have been debugging, the Rubygems `gem pristine [GEMNAME]` command may be inconvenient.
+One can avoid waiting for `gem pristine --all`, and instead run `bundle pristine`.

data/man/bundle-remove.1

@@ -0,0 +1,31 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-REMOVE" "1" "December 2018" "" ""
+.
+.SH "NAME"
+\fBbundle\-remove\fR \- Removes gems from the Gemfile
+.
+.SH "SYNOPSIS"
+\fBbundle remove [GEM [GEM \.\.\.]] [\-\-install]\fR
+.
+.SH "DESCRIPTION"
+Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid\. If a gem cannot be removed, a warning is printed\. If a gem is already absent from the Gemfile, and error is raised\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-install\fR
+Runs \fBbundle install\fR after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s)\.
+.
+.P
+Example:
+.
+.P
+bundle remove rails
+.
+.P
+bundle remove rails rack
+.
+.P
+bundle remove rails rack \-\-install

data/man/bundle-remove.1.txt

@@ -0,0 +1,34 @@
+BUNDLE-REMOVE(1)					      BUNDLE-REMOVE(1)
+
+
+
+NAME
+       bundle-remove - Removes gems from the Gemfile
+
+SYNOPSIS
+       bundle remove [GEM [GEM ...]] [--install]
+
+DESCRIPTION
+       Removes the given gems from the Gemfile while ensuring that the result-
+       ing Gemfile is still valid. If a gem cannot be removed,	a  warning  is
+       printed.  If  a	gem  is  already absent from the Gemfile, and error is
+       raised.
+
+OPTIONS
+       --install
+	      Runs bundle install after the given gems have been removed  from
+	      the  Gemfile,  which  ensures  that  both  the  lockfile and the
+	      installed gems on disk are also  updated	to  remove  the  given
+	      gem(s).
+
+       Example:
+
+       bundle remove rails
+
+       bundle remove rails rack
+
+       bundle remove rails rack --install
+
+
+
+				 December 2018		      BUNDLE-REMOVE(1)

data/man/bundle-remove.ronn

@@ -0,0 +1,23 @@
+bundle-remove(1) -- Removes gems from the Gemfile
+===========================================================================
+
+## SYNOPSIS
+
+`bundle remove [GEM [GEM ...]] [--install]`
+
+## DESCRIPTION
+
+Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid. If a gem cannot be removed, a warning is printed. If a gem is already absent from the Gemfile, and error is raised.
+
+## OPTIONS
+
+* `--install`:
+  Runs `bundle install` after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s).
+
+Example:
+
+bundle remove rails
+
+bundle remove rails rack
+
+bundle remove rails rack --install