bundler 2.1.4 → 2.2.18

data/man/bundle-add.1.txt

@@ -1,58 +0,0 @@
-BUNDLE-ADD(1)							 BUNDLE-ADD(1)
-
-
-
-NAME
-       bundle-add - Add gem to the Gemfile and run bundle install
-
-SYNOPSIS
-       bundle	  add	  GEM_NAME     [--group=GROUP]	   [--version=VERSION]
-       [--source=SOURCE]   [--git=GIT]	 [--branch=BRANCH]    [--skip-install]
-       [--strict] [--optimistic]
-
-DESCRIPTION
-       Adds  the  named  gem  to  the  Gemfile	and run bundle install. bundle
-       install can be avoided by using the flag --skip-install.
-
-       Example:
-
-       bundle add rails
-
-       bundle add rails --version "< 3.0, > 1.1"
-
-       bundle add rails  --version  "~>  5.0.0"  --source  "https://gems.exam-
-       ple.com" --group "development"
-
-       bundle add rails --skip-install
-
-       bundle add rails --group "development, test"
-
-OPTIONS
-       --version, -v
-	      Specify version requirements(s) for the added gem.
-
-       --group, -g
-	      Specify  the  group(s) for the added gem. Multiple groups should
-	      be separated by commas.
-
-       --source, , -s
-	      Specify the source for the added gem.
-
-       --git  Specify the git source for the added gem.
-
-       --branch
-	      Specify the git branch for the added gem.
-
-       --skip-install
-	      Adds the gem to the Gemfile but does not install it.
-
-       --optimistic
-	      Adds optimistic declaration of version
-
-       --strict
-	      Adds strict declaration of version
-
-
-
-
-				 January 2020			 BUNDLE-ADD(1)

data/man/bundle-binstubs.1.txt

@@ -1,48 +0,0 @@
-BUNDLE-BINSTUBS(1)					    BUNDLE-BINSTUBS(1)
-
-
-
-NAME
-       bundle-binstubs - Install the binstubs of the listed gems
-
-SYNOPSIS
-       bundle binstubs GEM_NAME [--force] [--path PATH] [--standalone]
-
-DESCRIPTION
-       Binstubs  are  scripts  that wrap around executables. Bundler creates a
-       small Ruby file (a binstub) that loads Bundler, runs the  command,  and
-       puts  it  into  bin/. Binstubs are a shortcut-or alternative- to always
-       using bundle exec. This gives you a file that can be run directly,  and
-       one  that  will always run the correct gem version used by the applica-
-       tion.
-
-       For example, if you run bundle binstubs rspec-core, Bundler will create
-       the file bin/rspec. That file will contain enough code to load Bundler,
-       tell it to load the bundled gems, and then run rspec.
-
-       This command generates binstubs for executables in  GEM_NAME.  Binstubs
-       are  put into bin, or the --path directory if one has been set. Calling
-       binstubs with [GEM [GEM]] will create binstubs for all given gems.
-
-OPTIONS
-       --force
-	      Overwrite existing binstubs if they exist.
-
-       --path The location to install the specified binstubs to. This defaults
-	      to bin.
-
-       --standalone
-	      Makes  binstubs  that  can work without depending on Rubygems or
-	      Bundler at runtime.
-
-       --shebang
-	      Specify a different shebang executable  name  than  the  default
-	      (default 'ruby')
-
-BUNDLE INSTALL --BINSTUBS
-       To  create  binstubs  for  all  the  gems in the bundle you can use the
-       --binstubs flag in bundle install(1) bundle-install.1.html.
-
-
-
-				 January 2020		    BUNDLE-BINSTUBS(1)

data/man/bundle-cache.1.txt

@@ -1,78 +0,0 @@
-BUNDLE-CACHE(1) 					       BUNDLE-CACHE(1)
-
-
-
-NAME
-       bundle-cache - Package your needed .gem files into your application
-
-SYNOPSIS
-       bundle cache
-
-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
-       The bundle cache 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.
-
-SUPPORT FOR MULTIPLE PLATFORMS
-       When using gems that have different packages for  different  platforms,
-       Bundler	supports caching of gems for other platforms where the Gemfile
-       has been resolved (i.e. present in the lockfile) in vendor/cache.  This
-       needs  to  be enabled via the --all-platforms option. This setting will
-       be remembered in your local bundler configuration.
-
-REMOTE FETCHING
-       By default, if you run bundle install(1)](bundle-install.1.html)  after
-       running bundle cache(1) bundle-cache.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):
-
-
-
-	   source "https://rubygems.org"
-
-	   gem "nokogiri"
-
-
-
-       If you run bundle cache under C Ruby, bundler will retrieve the version
-       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 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 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  "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 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 bundle cache on an identical machine and  check  in
-       the  gems. For instance, you can run bundle cache on an identical stag-
-       ing box during your staging process,  and  check  in  the  vendor/cache
-       before deploying to production.
-
-       By  default,  bundle  cache(1)  bundle-cache.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 cache --no-install.
-
-
-
-				 January 2020		       BUNDLE-CACHE(1)

data/man/bundle-check.1.txt

@@ -1,33 +0,0 @@
-BUNDLE-CHECK(1) 					       BUNDLE-CHECK(1)
-
-
-
-NAME
-       bundle-check - Verifies if dependencies are satisfied by installed gems
-
-SYNOPSIS
-       bundle check [--dry-run] [--gemfile=FILE] [--path=PATH]
-
-DESCRIPTION
-       check  searches the local machine for each of the gems requested in the
-       Gemfile. If all gems are found, Bundler prints a  success  message  and
-       exits with a status of 0.
-
-       If not, the first missing gem is listed and Bundler exits status 1.
-
-OPTIONS
-       --dry-run
-	      Locks the [Gemfile(5)][Gemfile(5)] before running the command.
-
-       --gemfile
-	      Use  the	specified  gemfile  instead  of  the [Gemfile(5)][Gem-
-	      file(5)].
-
-       --path Specify a different path than the system	default  ($BUNDLE_PATH
-	      or  $GEM_HOME).  Bundler	will  remember	this  value for future
-	      installs on this machine.
-
-
-
-
-				 January 2020		       BUNDLE-CHECK(1)

data/man/bundle-clean.1.txt

@@ -1,26 +0,0 @@
-BUNDLE-CLEAN(1) 					       BUNDLE-CLEAN(1)
-
-
-
-NAME
-       bundle-clean - Cleans up unused gems in your bundler directory
-
-SYNOPSIS
-       bundle clean [--dry-run] [--force]
-
-DESCRIPTION
-       This  command  will  remove  all unused gems in your bundler directory.
-       This is useful when you have made many changes to  your	gem  dependen-
-       cies.
-
-OPTIONS
-       --dry-run
-	      Print the changes, but do not clean the unused gems.
-
-       --force
-	      Force a clean even if --path is not set.
-
-
-
-
-				 January 2020		       BUNDLE-CLEAN(1)