bundler 1.15.4 → 1.16.0.pre.1

data/man/bundle-outdated.1.txt

@@ -0,0 +1,127 @@
+BUNDLE-OUTDATED(1)					    BUNDLE-OUTDATED(1)
+
+
+
+1mNAME0m
+       1mbundle-outdated 22m- List installed gems with newer versions available
+
+1mSYNOPSIS0m
+       1mbundle   outdated   22m[GEM]	[--local]   [--pre]  [--source]  [--strict]
+       [--parseable	|     --porcelain]     [--group=GROUP]	    [--groups]
+       [--update-strict]  [--patch|--minor|--major]  [--filter-major]  [--fil-
+       ter-minor] [--filter-patch]
+
+1mDESCRIPTION0m
+       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
+	      Do not attempt to fetch gems remotely  and  use  the  gem  cache
+	      instead.
+
+       1m--pre	22mCheck for newer pre-release gems.
+
+       1m--source0m
+	      Check against a specific source.
+
+       1m--strict0m
+	      Only list newer versions allowed by your Gemfile requirements.
+
+       1m--parseable22m, 1m--porcelain0m
+	      Use minimal formatting for more parseable output.
+
+       1m--group0m
+	      List gems from a specific group.
+
+       1m--groups0m
+	      List gems organized by groups.
+
+       1m--update-strict0m
+	      Strict  conservative  resolution,  do  not  allow  any gem to be
+	      updated past latest --patch | --minor| --major.
+
+       1m--minor0m
+	      Prefer updating only to next minor version.
+
+       1m--major0m
+	      Prefer updating to next major version (default).
+
+       1m--patch0m
+	      Prefer updating only to next patch version.
+
+       1m--filter-major0m
+	      Only list major newer versions.
+
+       1m--filter-minor0m
+	      Only list minor newer versions.
+
+       1m--filter-patch0m
+	      Only list patch newer versions.
+
+1mPATCH LEVEL OPTIONS0m
+       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.
+
+1mFILTERING OUTPUT0m
+       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:
+
+
+
+	   * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test"
+	   * hashie (newest 3.4.6, installed 1.2.0, requested = 1.2.0) in groups "default"
+	   * headless (newest 2.3.1, installed 2.2.3) in groups "test"
+
+
+
+       1m--filter-major 22mwould only show:
+
+
+
+	   * hashie (newest 3.4.6, installed 1.2.0, requested = 1.2.0) in groups "default"
+
+
+
+       1m--filter-minor 22mwould only show:
+
+
+
+	   * headless (newest 2.3.1, installed 2.2.3) in groups "test"
+
+
+
+       1m--filter-patch 22mwould only show:
+
+
+
+	   * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test"
+
+
+
+       Filter options can be combined. 1m--filter-minor 22mand 1m--filter-patch 22mwould
+       show:
+
+
+
+	   * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test"
+	   * headless (newest 2.3.1, installed 2.2.3) in groups "test"
+
+
+
+       Combining all three 1mfilter 22moptions would be the same result as  provid-
+       ing none of them.
+
+
+
+				  August 2017		    BUNDLE-OUTDATED(1)

data/man/bundle-outdated.ronn

@@ -37,7 +37,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`:

data/man/bundle-package.1

@@ -0,0 +1,55 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-PACKAGE" "1" "August 2017" "" ""
+.
+.SH "NAME"
+\fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
+.
+.SH "SYNOPSIS"
+\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)][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\.
+.
+.SH "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 \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)][bundle\-install] after running [bundle package(1)][bundle\-package], 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):
+.
+.IP "" 4
+.
+.nf
+
+source "https://rubygems\.org"
+
+gem "nokogiri"
+.
+.fi
+.
+.IP "" 0
+.
+.P
+If you run \fBbundle package\fR under C Ruby, bundler will retrieve the version of \fBnokogiri\fR for the \fB"ruby"\fR platform\. If you deploy to JRuby and run \fBbundle install\fR, bundler is forced to check to see whether a \fB"java"\fR platformed \fBnokogiri\fR exists\.
+.
+.P
+Even though the \fBnokogiri\fR gem for the Ruby platform is \fItechnically\fR acceptable on JRuby, it has a C extension that does not run on JRuby\. As a result, bundler will, by default, still connect to \fBrubygems\.org\fR to check whether it has a version of one of your gems more specific to your platform\.
+.
+.P
+This problem is also not limited to the \fB"java"\fR 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\.
+.
+.P
+If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriate for the platform you are on, you can run \fBbundle install \-\-local\fR to skip checking for more appropriate gems, and use the ones in \fBvendor/cache\fR\.
+.
+.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)][bundle\-package] 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

@@ -0,0 +1,79 @@
+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)][bundle-install], 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
+       remembered.
+
+1mSUPPORT FOR MULTIPLE PLATFORMS0m
+       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.
+       This setting will be remembered in your local bundler configuration.
+
+1mREMOTE FETCHING0m
+       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.
+
+       For instance, consider this Gemfile(5):
+
+
+
+	   source "https://rubygems.org"
+
+	   gem "nokogiri"
+
+
+
+       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.
+
+       Even  though  the  1mnokogiri  22mgem  for  the Ruby platform is 4mtechnically0m
+       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
+       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
+       (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.
+
+       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
+       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.
+
+
+
+				  August 2017		     BUNDLE-PACKAGE(1)

data/man/bundle-package.ronn

@@ -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] 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

@@ -0,0 +1,61 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-PLATFORM" "1" "June 2017" "" ""
+.
+.SH "NAME"
+\fBbundle\-platform\fR \- Displays platform compatibility information
+.
+.SH "SYNOPSIS"
+\fBbundle platform\fR [\-\-ruby]
+.
+.SH "DESCRIPTION"
+\fBplatform\fR will display information from your Gemfile, Gemfile\.lock, and Ruby VM about your platform\.
+.
+.P
+For instance, using this Gemfile(5):
+.
+.IP "" 4
+.
+.nf
+
+source "https://rubygems\.org"
+
+ruby "1\.9\.3"
+
+gem "rack"
+.
+.fi
+.
+.IP "" 0
+.
+.P
+If you run \fBbundle platform\fR on Ruby 1\.9\.3, it will display the following output:
+.
+.IP "" 4
+.
+.nf
+
+Your platform is: x86_64\-linux
+
+Your app has gems that work on these platforms:
+* ruby
+
+Your Gemfile specifies a Ruby version requirement:
+* ruby 1\.9\.3
+
+Your current platform satisfies the Ruby version requirement\.
+.
+.fi
+.
+.IP "" 0
+.
+.P
+\fBplatform\fR will list all the platforms in your \fBGemfile\.lock\fR as well as the \fBruby\fR directive if applicable from your Gemfile(5)\. It will also let you know if the \fBruby\fR directive requirement has been met\. If \fBruby\fR directive doesn\'t match the running Ruby VM, it will tell you what part does not\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-ruby\fR
+It will display the ruby directive information, so you don\'t have to parse it from the Gemfile(5)\.
+

data/man/bundle-platform.1.txt

@@ -0,0 +1,57 @@
+BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
+
+
+
+1mNAME0m
+       1mbundle-platform 22m- Displays platform compatibility information
+
+1mSYNOPSIS0m
+       1mbundle platform 22m[--ruby]
+
+1mDESCRIPTION0m
+       1mplatform  22mwill display information from your Gemfile, Gemfile.lock, and
+       Ruby VM about your platform.
+
+       For instance, using this Gemfile(5):
+
+
+
+	   source "https://rubygems.org"
+
+	   ruby "1.9.3"
+
+	   gem "rack"
+
+
+
+       If you run 1mbundle platform 22mon Ruby 1.9.3, it will display the following
+       output:
+
+
+
+	   Your platform is: x86_64-linux
+
+	   Your app has gems that work on these platforms:
+	   * ruby
+
+	   Your Gemfile specifies a Ruby version requirement:
+	   * ruby 1.9.3
+
+	   Your current platform satisfies the Ruby version requirement.
+
+
+
+       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-
+       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
+	      have to parse it from the Gemfile(5).
+
+
+
+
+				   June 2017		    BUNDLE-PLATFORM(1)

data/man/bundle-pristine.1

@@ -0,0 +1,34 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-PRISTINE" "1" "August 2017" "" ""
+.
+.SH "NAME"
+\fBbundle\-pristine\fR \- Restores installed gems to their pristine condition
+.
+.SH "SYNOPSIS"
+\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\.
+.
+.P
+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

@@ -0,0 +1,44 @@
+BUNDLE-PRISTINE(1)					    BUNDLE-PRISTINE(1)
+
+
+
+1mNAME0m
+       1mbundle-pristine 22m- Restores installed gems to their pristine condition
+
+1mSYNOPSIS0m
+       1mbundle pristine0m
+
+1mDESCRIPTION0m
+       1mpristine  22mrestores	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.
+
+       For  further  explanation,  1mbundle  pristine  22mignores unpacked files on
+       disk. In other words, this command utilizes the local 1m.gem 22mcache 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
+       1mpristine22m. One also cannot use 1mbundle pristine 22mon  gems  with  a  'path'
+       option  in  the	Gemfile,  because  bundler has no original copy it can
+       restore from.
+
+       When is it practical to use 1mbundle pristine22m?
+
+       It comes in handy when a developer is debugging a gem. 1mbundle	pristine0m
+       is a great way to get rid of experimental changes to a gem that one may
+       not want.
+
+       Why use 1mbundle pristine 22mover 1mgem pristine --all22m?
+
+       Both commands are very similar. For context: 1mbundle  pristine22m,  without
+       arguments,  cleans  all gems from the lockfile. Meanwhile, 1mgem pristine0m
+       1m--all 22mcleans all installed gems for that Ruby version.
+
+       If a developer forgets which gems in their project they might have been
+       debugging,  the Rubygems 1mgem pristine [GEMNAME] 22mcommand may be inconve-
+       nient. One can avoid waiting for 1mgem pristine --all22m,  and  instead	run
+       1mbundle pristine22m.
+
+
+
+				  August 2017		    BUNDLE-PRISTINE(1)