bundler 1.9.0 → 1.17.3

data/man/bundle-list.1

@@ -0,0 +1,50 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-LIST" "1" "December 2018" "" ""
+.
+.SH "NAME"
+\fBbundle\-list\fR \- List all the gems in the bundle
+.
+.SH "SYNOPSIS"
+\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

@@ -0,0 +1,43 @@
+BUNDLE-LIST(1)							BUNDLE-LIST(1)
+
+
+
+NAME
+       bundle-list - List all the gems in the bundle
+
+SYNOPSIS
+       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.
+
+
+
+
+				 December 2018			BUNDLE-LIST(1)

data/man/bundle-list.ronn

@@ -0,0 +1,33 @@
+bundle-list(1) -- List all the gems in the bundle
+=========================================================================
+
+## SYNOPSIS
+
+`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

@@ -0,0 +1,84 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-LOCK" "1" "November 2018" "" ""
+.
+.SH "NAME"
+\fBbundle\-lock\fR \- Creates / Updates a lockfile without installing
+.
+.SH "SYNOPSIS"
+\fBbundle lock\fR [\-\-update] [\-\-local] [\-\-print] [\-\-lockfile=PATH] [\-\-full\-index] [\-\-add\-platform] [\-\-remove\-platform] [\-\-patch] [\-\-minor] [\-\-major] [\-\-strict] [\-\-conservative]
+.
+.SH "DESCRIPTION"
+Lock the gems specified in Gemfile\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-update=<*gems>\fR
+Ignores the existing lockfile\. Resolve then updates lockfile\. Taking a list of gems or updating all gems if no list is given\.
+.
+.TP
+\fB\-\-local\fR
+Do not attempt to connect to \fBrubygems\.org\fR\. Instead, Bundler will use the gems already present in Rubygems\' cache or in \fBvendor/cache\fR\. Note that if a appropriate platform\-specific gem exists on \fBrubygems\.org\fR it will not be found\.
+.
+.TP
+\fB\-\-print\fR
+Prints the lockfile to STDOUT instead of writing to the file system\.
+.
+.TP
+\fB\-\-lockfile=<path>\fR
+The path where the lockfile should be written to\.
+.
+.TP
+\fB\-\-full\-index\fR
+Fall back to using the single\-file index of all gems\.
+.
+.TP
+\fB\-\-add\-platform\fR
+Add a new platform to the lockfile, re\-resolving for the addition of that platform\.
+.
+.TP
+\fB\-\-remove\-platform\fR
+Remove a platform from the lockfile\.
+.
+.TP
+\fB\-\-patch\fR
+If updating, prefer updating only to next patch version\.
+.
+.TP
+\fB\-\-minor\fR
+If updating, prefer updating only to next minor version\.
+.
+.TP
+\fB\-\-major\fR
+If updating, prefer updating to next major version (default)\.
+.
+.TP
+\fB\-\-strict\fR
+If updating, do not allow any gem to be updated past latest \-\-patch | \-\-minor | \-\-major\.
+.
+.TP
+\fB\-\-conservative\fR
+If updating, use bundle install conservative update behavior and do not allow shared dependencies to be updated\.
+.
+.SH "UPDATING ALL GEMS"
+If you run \fBbundle lock\fR with \fB\-\-update\fR 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\.
+.
+.SH "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 \fBGemfile\.lock\fR\.
+.
+.P
+For instance, you only want to update \fBnokogiri\fR, run \fBbundle lock \-\-update nokogiri\fR\.
+.
+.P
+Bundler will update \fBnokogiri\fR and any of its dependencies, but leave the rest of the gems that you specified locked to the versions in the \fBGemfile\.lock\fR\.
+.
+.SH "SUPPORTING OTHER PLATFORMS"
+If you want your bundle to support platforms other than the one you\'re running locally, you can run \fBbundle lock \-\-add\-platform PLATFORM\fR 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\.
+.
+.P
+For a full explanation of gem platforms, see \fBgem help platform\fR\.
+.
+.SH "PATCH LEVEL OPTIONS"
+See bundle update(1) \fIbundle\-update\.1\.html\fR for details\.

data/man/bundle-lock.1.txt

@@ -0,0 +1,93 @@
+BUNDLE-LOCK(1)							BUNDLE-LOCK(1)
+
+
+
+NAME
+       bundle-lock - Creates / Updates a lockfile without installing
+
+SYNOPSIS
+       bundle	 lock	[--update]   [--local]	 [--print]   [--lockfile=PATH]
+       [--full-index] [--add-platform] [--remove-platform] [--patch] [--minor]
+       [--major] [--strict] [--conservative]
+
+DESCRIPTION
+       Lock the gems specified in Gemfile.
+
+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.
+
+       --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.
+
+       --print
+	      Prints the lockfile to STDOUT instead of	writing  to  the  file
+	      system.
+
+       --lockfile=<path>
+	      The path where the lockfile should be written to.
+
+       --full-index
+	      Fall back to using the single-file index of all gems.
+
+       --add-platform
+	      Add  a  new platform to the lockfile, re-resolving for the addi-
+	      tion of that platform.
+
+       --remove-platform
+	      Remove a platform from the lockfile.
+
+       --patch
+	      If updating, prefer updating only to next patch version.
+
+       --minor
+	      If updating, prefer updating only to next minor version.
+
+       --major
+	      If updating, prefer updating to next major version (default).
+
+       --strict
+	      If updating, do not allow any gem  to  be  updated  past	latest
+	      --patch | --minor | --major.
+
+       --conservative
+	      If updating, use bundle install conservative update behavior and
+	      do not allow shared dependencies to be updated.
+
+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.
+
+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
+       Gemfile.lock.
+
+       For  instance,  you  only  want	to  update  nokogiri,  run bundle lock
+       --update nokogiri.
+
+       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.
+
+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 gem help platform.
+
+PATCH LEVEL OPTIONS
+       See bundle update(1) bundle-update.1.html for details.
+
+
+
+				 November 2018			BUNDLE-LOCK(1)

data/man/bundle-lock.ronn

@@ -0,0 +1,94 @@
+bundle-lock(1) -- Creates / Updates a lockfile without installing
+=================================================================
+
+## SYNOPSIS
+
+`bundle lock` [--update]
+              [--local]
+              [--print]
+              [--lockfile=PATH]
+              [--full-index]
+              [--add-platform]
+              [--remove-platform]
+              [--patch]
+              [--minor]
+              [--major]
+              [--strict]
+              [--conservative]
+
+## DESCRIPTION
+
+Lock the gems specified in Gemfile.
+
+## 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.
+
+* `--local`:
+  Do not attempt to connect to `rubygems.org`. Instead, Bundler will use the
+  gems already present in Rubygems' cache or in `vendor/cache`. Note that if a
+  appropriate platform-specific gem exists on `rubygems.org` it will not be
+  found.
+
+* `--print`:
+  Prints the lockfile to STDOUT instead of writing to the file system.
+
+* `--lockfile=<path>`:
+  The path where the lockfile should be written to.
+
+* `--full-index`:
+  Fall back to using the single-file index of all gems.
+
+* `--add-platform`:
+  Add a new platform to the lockfile, re-resolving for the addition of that
+  platform.
+
+* `--remove-platform`:
+  Remove a platform from the lockfile.
+
+* `--patch`:
+  If updating, prefer updating only to next patch version.
+
+* `--minor`:
+  If updating, prefer updating only to next minor version.
+
+* `--major`:
+  If updating, prefer updating to next major version (default).
+
+* `--strict`:
+  If updating, do not allow any gem to be updated past latest --patch | --minor | --major.
+
+* `--conservative`:
+  If updating, use bundle install conservative update behavior and do not allow shared dependencies to be updated.
+
+## 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.
+
+## 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 `Gemfile.lock`.
+
+For instance, you only want to update `nokogiri`, run `bundle lock --update nokogiri`.
+
+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 `Gemfile.lock`.
+
+## 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 `gem help platform`.
+
+## PATCH LEVEL OPTIONS
+
+See [bundle update(1)](bundle-update.1.html) for details.

data/man/bundle-open.1

@@ -0,0 +1,32 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-OPEN" "1" "November 2018" "" ""
+.
+.SH "NAME"
+\fBbundle\-open\fR \- Opens the source directory for a gem in your bundle
+.
+.SH "SYNOPSIS"
+\fBbundle open\fR [GEM]
+.
+.SH "DESCRIPTION"
+Opens the source directory of the provided GEM in your editor\.
+.
+.P
+For this to work the \fBEDITOR\fR or \fBBUNDLER_EDITOR\fR environment variable has to be set\.
+.
+.P
+Example:
+.
+.IP "" 4
+.
+.nf
+
+bundle open \'rack\'
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Will open the source directory for the \'rack\' gem in your bundle\.

data/man/bundle-open.1.txt

@@ -0,0 +1,29 @@
+BUNDLE-OPEN(1)							BUNDLE-OPEN(1)
+
+
+
+NAME
+       bundle-open - Opens the source directory for a gem in your bundle
+
+SYNOPSIS
+       bundle open [GEM]
+
+DESCRIPTION
+       Opens the source directory of the provided GEM in your editor.
+
+       For  this to work the EDITOR or BUNDLER_EDITOR environment variable has
+       to be set.
+
+       Example:
+
+
+
+	   bundle open 'rack'
+
+
+
+       Will open the source directory for the 'rack' gem in your bundle.
+
+
+
+				 November 2018			BUNDLE-OPEN(1)