summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2019-01-04 13:10:58 +0000
committerhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2019-01-04 13:10:58 +0000
commite97741e12a22d78825a3a9dfcb7382adb0e27855 (patch)
tree5344cb31a89df6fd5fbae92740d4229d655eee8f /man
parent4bbbbb6a3f5bd242f740041a644311f97c4a0052 (diff)
Merge Bundler 2.0.1 from upstream.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'man')
-rw-r--r--man/bundle-add.1.txt4
-rw-r--r--man/bundle-check.1.txt4
-rw-r--r--man/bundle-config.12
-rw-r--r--man/bundle-config.1.txt177
-rw-r--r--man/bundle-exec.1.txt30
-rw-r--r--man/bundle-gem.1.txt22
-rw-r--r--man/bundle-install.12
-rw-r--r--man/bundle-install.1.txt74
-rw-r--r--man/bundle-lock.1.txt14
-rw-r--r--man/bundle-outdated.1.txt14
-rw-r--r--man/bundle-package.1.txt16
-rw-r--r--man/bundle-pristine.1.txt6
-rw-r--r--man/bundle-remove.1.txt4
-rw-r--r--man/bundle-update.12
-rw-r--r--man/bundle-update.1.txt56
-rw-r--r--man/bundle.16
-rw-r--r--man/bundle.1.txt9
-rw-r--r--man/bundle.ronn3
-rw-r--r--man/gemfile.510
-rw-r--r--man/gemfile.5.ronn8
-rw-r--r--man/gemfile.5.txt70
21 files changed, 271 insertions, 262 deletions
diff --git a/man/bundle-add.1.txt b/man/bundle-add.1.txt
index 653a166044..ccc101a552 100644
--- a/man/bundle-add.1.txt
+++ b/man/bundle-add.1.txt
@@ -10,8 +10,8 @@ BUNDLE-ADD(1) BUNDLE-ADD(1)
[--source=SOURCE] [--skip-install] [--strict] [--optimistic]
1mDESCRIPTION0m
- Adds the named gem to the Gemfile and run 1mbundle install22m. 1mbundle0m
- 1minstall 22mcan be avoided by using the flag 1m--skip-install22m.
+ Adds the named gem to the Gemfile and run 1mbundle install22m. 1mbundle in-0m
+ 1mstall 22mcan be avoided by using the flag 1m--skip-install22m.
Example:
diff --git a/man/bundle-check.1.txt b/man/bundle-check.1.txt
index 20cfe26446..afb3fb84f6 100644
--- a/man/bundle-check.1.txt
+++ b/man/bundle-check.1.txt
@@ -24,8 +24,8 @@ BUNDLE-CHECK(1) BUNDLE-CHECK(1)
file(5)].
1m--path 22mSpecify a different path than the system default (1m$BUNDLE_PATH0m
- or 1m$GEM_HOME22m). Bundler will remember this value for future
- installs on this machine.
+ or 1m$GEM_HOME22m). Bundler will remember this value for future in-
+ stalls on this machine.
diff --git a/man/bundle-config.1 b/man/bundle-config.1
index 80ef0c0715..9f6faa1201 100644
--- a/man/bundle-config.1
+++ b/man/bundle-config.1
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "BUNDLE\-CONFIG" "1" "December 2018" "" ""
+.TH "BUNDLE\-CONFIG" "1" "January 2019" "" ""
.
.SH "NAME"
\fBbundle\-config\fR \- Set bundler configuration options
diff --git a/man/bundle-config.1.txt b/man/bundle-config.1.txt
index f8f421c3db..648edc1b0c 100644
--- a/man/bundle-config.1.txt
+++ b/man/bundle-config.1.txt
@@ -44,8 +44,8 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
1mapp/.bundle/config22m.
Executing 1mbundle config --delete <name> 22mwill delete the configuration
- in both local and global sources. Not compatible with --global or
- --local flag.
+ in both local and global sources. Not compatible with --global or --lo-
+ cal flag.
Executing bundle with the 1mBUNDLE_IGNORE_CONFIG 22menvironment variable set
will cause it to ignore all configuration.
@@ -68,13 +68,13 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
text. If used, you might add this directory to your environ-
ment's 1mPATH 22mvariable. For instance, if the 1mrails 22mgem comes with
a 1mrails 22mexecutable, this flag will create a 1mbin/rails 22mexecutable
- that ensures that all referred dependencies will be resolved
- using the bundled gems.
+ that ensures that all referred dependencies will be resolved us-
+ ing the bundled gems.
1mdeployment0m
In deployment mode, Bundler will 'roll-out' the bundle for 1mpro-0m
- 1mduction 22muse. Please check carefully if you want to have this
- option enabled in 1mdevelopment 22mor 1mtest 22menvironments.
+ 1mduction 22muse. Please check carefully if you want to have this op-
+ tion enabled in 1mdevelopment 22mor 1mtest 22menvironments.
1mpath 22mThe location to install the specified gems to. This defaults to
Rubygems' setting. Bundler shares this location with Rubygems,
@@ -143,8 +143,8 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
4mdle-install.1.html24m.
o 1mallow_bundler_dependency_conflicts 22m(1mBUNDLE_ALLOW_BUNDLER_DEPEN-0m
- 1mDENCY_CONFLICTS22m): Allow resolving to specifications that have
- dependencies on 1mbundler 22mthat are incompatible with the running
+ 1mDENCY_CONFLICTS22m): Allow resolving to specifications that have de-
+ pendencies on 1mbundler 22mthat are incompatible with the running
Bundler version.
o 1mallow_deployment_source_credential_changes 22m(1mBUNDLE_ALLOW_DEPLOY-0m
@@ -160,8 +160,8 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
cally run 1mbundle clean 22mafter installing when an explicit 1mpath 22mhas
not been set and Bundler is not installing into the system gems.
- o 1mauto_install 22m(1mBUNDLE_AUTO_INSTALL22m): Automatically run 1mbundle0m
- 1minstall 22mwhen gems are missing.
+ o 1mauto_install 22m(1mBUNDLE_AUTO_INSTALL22m): Automatically run 1mbundle in-0m
+ 1mstall 22mwhen gems are missing.
o 1mbin 22m(1mBUNDLE_BIN22m): Install executables from gems in the bundle to
the specified directory. Defaults to 1mfalse22m.
@@ -183,8 +183,8 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
Defaults to 1mirb22m.
o 1mdefault_install_uses_path 22m(1mBUNDLE_DEFAULT_INSTALL_USES_PATH22m):
- Whether a 1mbundle install 22mwithout an explicit 1m--path 22margument
- defaults to installing gems in 1m.bundle22m.
+ Whether a 1mbundle install 22mwithout an explicit 1m--path 22margument de-
+ faults to installing gems in 1m.bundle22m.
o 1mdeployment 22m(1mBUNDLE_DEPLOYMENT22m): Disallow changes to the 1mGemfile22m.
When the 1mGemfile 22mis changed and the lockfile has not been updated,
@@ -194,12 +194,12 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
Allow installing gems even if they do not match the checksum pro-
vided by RubyGems.
- o 1mdisable_exec_load 22m(1mBUNDLE_DISABLE_EXEC_LOAD22m): Stop Bundler from
- using 1mload 22mto launch an executable in-process in 1mbundle exec22m.
+ o 1mdisable_exec_load 22m(1mBUNDLE_DISABLE_EXEC_LOAD22m): Stop Bundler from us-
+ ing 1mload 22mto launch an executable in-process in 1mbundle exec22m.
- o 1mdisable_local_branch_check 22m(1mBUNDLE_DISABLE_LOCAL_BRANCH_CHECK22m):
- Allow Bundler to use a local git override without a branch speci-
- fied in the Gemfile.
+ o 1mdisable_local_branch_check 22m(1mBUNDLE_DISABLE_LOCAL_BRANCH_CHECK22m): Al-
+ low Bundler to use a local git override without a branch specified
+ in the Gemfile.
o 1mdisable_multisource 22m(1mBUNDLE_DISABLE_MULTISOURCE22m): When set, Gem-
files containing multiple sources will produce errors instead of
@@ -242,90 +242,89 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
cache all gems globally, rather than locally to the installing Ruby
installation.
- o 1mglobal_path_appends_ruby_scope 22m(1mBUN-0m
- 1mDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE22m): Whether Bundler should append
- the Ruby scope (e.g. engine and ABI version) to a globally-config-
- ured path.
+ o 1mglobal_path_appends_ruby_scope 22m(1mBUNDLE_GLOBAL_PATH_AP-0m
+ 1mPENDS_RUBY_SCOPE22m): Whether Bundler should append the Ruby scope
+ (e.g. engine and ABI version) to a globally-configured path.
o 1mignore_messages 22m(1mBUNDLE_IGNORE_MESSAGES22m): When set, no post install
messages will be printed. To silence a single gem, use dot notation
like 1mignore_messages.httparty true22m.
- o 1minit_gems_rb 22m(1mBUNDLE_INIT_GEMS_RB22m) Generate a 1mgems.rb 22minstead of a
+ o 1minit_gems_rb 22m(1mBUNDLE_INIT_GEMS_RB22m) Generate a 1mgems.rb 22minstead of a
1mGemfile 22mwhen running 1mbundle init22m.
- o 1mjobs 22m(1mBUNDLE_JOBS22m): The number of gems Bundler can install in par-
+ o 1mjobs 22m(1mBUNDLE_JOBS22m): The number of gems Bundler can install in par-
allel. Defaults to 1.
o 1mlist_command 22m(1mBUNDLE_LIST_COMMAND22m) Enable new list command feature
- o 1mmajor_deprecations 22m(1mBUNDLE_MAJOR_DEPRECATIONS22m): Whether Bundler
+ o 1mmajor_deprecations 22m(1mBUNDLE_MAJOR_DEPRECATIONS22m): Whether Bundler
should print deprecation warnings for behavior that will be changed
in the next major version.
- o 1mno_install 22m(1mBUNDLE_NO_INSTALL22m): Whether 1mbundle package 22mshould skip
+ o 1mno_install 22m(1mBUNDLE_NO_INSTALL22m): Whether 1mbundle package 22mshould skip
installing gems.
- o 1mno_prune 22m(1mBUNDLE_NO_PRUNE22m): Whether Bundler should leave outdated
+ o 1mno_prune 22m(1mBUNDLE_NO_PRUNE22m): Whether Bundler should leave outdated
gems unpruned when caching.
o 1monly_update_to_newer_versions 22m(1mBUNDLE_ONLY_UPDATE_TO_NEWER_VER-0m
1mSIONS22m): During 1mbundle update22m, only resolve to newer versions of the
gems in the lockfile.
- o 1mpath 22m(1mBUNDLE_PATH22m): The location on disk where all gems in your
+ o 1mpath 22m(1mBUNDLE_PATH22m): The location on disk where all gems in your
bundle will be located regardless of 1m$GEM_HOME 22mor 1m$GEM_PATH 22mvalues.
- Bundle gems not found in this location will be installed by 1mbundle0m
- 1minstall22m. Defaults to 1mGem.dir22m. When --deployment is used, defaults
+ Bundle gems not found in this location will be installed by 1mbundle0m
+ 1minstall22m. Defaults to 1mGem.dir22m. When --deployment is used, defaults
to vendor/bundle.
- o 1mpath.system 22m(1mBUNDLE_PATH__SYSTEM22m): Whether Bundler will install
+ o 1mpath.system 22m(1mBUNDLE_PATH__SYSTEM22m): Whether Bundler will install
gems into the default system path (1mGem.dir22m).
- o 1mpath_relative_to_cwd 22m(1mPATH_RELATIVE_TO_CWD22m) Makes 1m--path 22mrelative
+ o 1mpath_relative_to_cwd 22m(1mPATH_RELATIVE_TO_CWD22m) Makes 1m--path 22mrelative
to the CWD instead of the 1mGemfile22m.
o 1mplugins 22m(1mBUNDLE_PLUGINS22m): Enable Bundler's experimental plugin sys-
tem.
- o 1mprefer_gems_rb 22m(1mBUNDLE_PREFER_GEMS_RB22m) Prefer 1mgems.rb 22mto 1mGemfile0m
+ o 1mprefer_gems_rb 22m(1mBUNDLE_PREFER_GEMS_RB22m) Prefer 1mgems.rb 22mto 1mGemfile0m
when Bundler is searching for a Gemfile.
- o 1mprint_only_version_number 22m(1mBUNDLE_PRINT_ONLY_VERSION_NUMBER22m) Print
+ o 1mprint_only_version_number 22m(1mBUNDLE_PRINT_ONLY_VERSION_NUMBER22m) Print
only version number from 1mbundler --version22m.
- o 1mredirect 22m(1mBUNDLE_REDIRECT22m): The number of redirects allowed for
+ o 1mredirect 22m(1mBUNDLE_REDIRECT22m): The number of redirects allowed for
network requests. Defaults to 1m522m.
- o 1mretry 22m(1mBUNDLE_RETRY22m): The number of times to retry failed network
+ o 1mretry 22m(1mBUNDLE_RETRY22m): The number of times to retry failed network
requests. Defaults to 1m322m.
o 1msetup_makes_kernel_gem_public 22m(1mBUNDLE_SETUP_MAKES_KERNEL_GEM_PUB-0m
- 1mLIC22m): Have 1mBundler.setup 22mmake the 1mKernel#gem 22mmethod public, even
+ 1mLIC22m): Have 1mBundler.setup 22mmake the 1mKernel#gem 22mmethod public, even
though RubyGems declares it as private.
- o 1mshebang 22m(1mBUNDLE_SHEBANG22m): The program name that should be invoked
- for generated binstubs. Defaults to the ruby install name used to
+ o 1mshebang 22m(1mBUNDLE_SHEBANG22m): The program name that should be invoked
+ for generated binstubs. Defaults to the ruby install name used to
generate the binstub.
- o 1msilence_root_warning 22m(1mBUNDLE_SILENCE_ROOT_WARNING22m): Silence the
+ o 1msilence_root_warning 22m(1mBUNDLE_SILENCE_ROOT_WARNING22m): Silence the
warning Bundler prints when installing gems as root.
o 1mskip_default_git_sources 22m(1mBUNDLE_SKIP_DEFAULT_GIT_SOURCES22m): Whether
Bundler should skip adding default git source shortcuts to the Gem-
file DSL.
- o 1mspecific_platform 22m(1mBUNDLE_SPECIFIC_PLATFORM22m): Allow bundler to
- resolve for the specific running platform and store it in the lock-
+ o 1mspecific_platform 22m(1mBUNDLE_SPECIFIC_PLATFORM22m): Allow bundler to re-
+ solve for the specific running platform and store it in the lock-
file, instead of only using a generic platform. A specific platform
- is the exact platform triple reported by 1mGem::Platform.local22m, such
- as 1mx86_64-darwin-16 22mor 1muniversal-java-1.822m. On the other hand,
- generic platforms are those such as 1mruby22m, 1mmswin22m, or 1mjava22m. In this
- example, 1mx86_64-darwin-16 22mwould map to 1mruby 22mand 1muniversal-java-1.80m
+ is the exact platform triple reported by 1mGem::Platform.local22m, such
+ as 1mx86_64-darwin-16 22mor 1muniversal-java-1.822m. On the other hand,
+ generic platforms are those such as 1mruby22m, 1mmswin22m, or 1mjava22m. In this
+ example, 1mx86_64-darwin-16 22mwould map to 1mruby 22mand 1muniversal-java-1.80m
to 1mjava22m.
- o 1mssl_ca_cert 22m(1mBUNDLE_SSL_CA_CERT22m): Path to a designated CA certifi-
- cate file or folder containing multiple certificates for trusted
+ o 1mssl_ca_cert 22m(1mBUNDLE_SSL_CA_CERT22m): Path to a designated CA certifi-
+ cate file or folder containing multiple certificates for trusted
CAs in PEM format.
o 1mssl_client_cert 22m(1mBUNDLE_SSL_CLIENT_CERT22m): Path to a designated file
@@ -335,46 +334,46 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
Bundler uses when making HTTPS requests. Defaults to verify peer.
o 1msuppress_install_using_messages 22m(1mBUNDLE_SUPPRESS_INSTALL_USING_MES-0m
- 1mSAGES22m): Avoid printing 1mUsing ... 22mmessages during installation when
+ 1mSAGES22m): Avoid printing 1mUsing ... 22mmessages during installation when
the version of a gem has not changed.
- o 1msystem_bindir 22m(1mBUNDLE_SYSTEM_BINDIR22m): The location where RubyGems
+ o 1msystem_bindir 22m(1mBUNDLE_SYSTEM_BINDIR22m): The location where RubyGems
installs binstubs. Defaults to 1mGem.bindir22m.
o 1mtimeout 22m(1mBUNDLE_TIMEOUT22m): The seconds allowed before timing out for
network requests. Defaults to 1m1022m.
o 1munlock_source_unlocks_spec 22m(1mBUNDLE_UNLOCK_SOURCE_UNLOCKS_SPEC22m):
- Whether running 1mbundle update --source NAME 22munlocks a gem with the
+ Whether running 1mbundle update --source NAME 22munlocks a gem with the
given name. Defaults to 1mtrue22m.
- o 1mupdate_requires_all_flag 22m(1mBUNDLE_UPDATE_REQUIRES_ALL_FLAG22m) Require
- passing 1m--all 22mto 1mbundle update 22mwhen everything should be updated,
+ o 1mupdate_requires_all_flag 22m(1mBUNDLE_UPDATE_REQUIRES_ALL_FLAG22m) Require
+ passing 1m--all 22mto 1mbundle update 22mwhen everything should be updated,
and disallow passing no options to 1mbundle update22m.
- o 1muser_agent 22m(1mBUNDLE_USER_AGENT22m): The custom user agent fragment
+ o 1muser_agent 22m(1mBUNDLE_USER_AGENT22m): The custom user agent fragment
Bundler includes in API requests.
o 1mwith 22m(1mBUNDLE_WITH22m): A 1m:22m-separated list of groups whose gems bundler
should install.
- o 1mwithout 22m(1mBUNDLE_WITHOUT22m): A 1m:22m-separated list of groups whose gems
+ o 1mwithout 22m(1mBUNDLE_WITHOUT22m): A 1m:22m-separated list of groups whose gems
bundler should not install.
- In general, you should set these settings per-application by using the
- applicable flag to the bundle install(1) 4mbundle-install.1.html24m or bun-
+ In general, you should set these settings per-application by using the
+ applicable flag to the bundle install(1) 4mbundle-install.1.html24m or bun-
dle package(1) 4mbundle-package.1.html24m command.
- You can set them globally either via environment variables or 1mbundle0m
- 1mconfig22m, whichever is preferable for your setup. If you use both, envi-
+ You can set them globally either via environment variables or 1mbundle0m
+ 1mconfig22m, whichever is preferable for your setup. If you use both, envi-
ronment variables will take preference over global settings.
1mLOCAL GIT REPOS0m
- Bundler also allows you to work against a git repository locally
- instead of using the remote version. This can be achieved by setting up
- a local override:
+ Bundler also allows you to work against a git repository locally in-
+ stead of using the remote version. This can be achieved by setting up a
+ local override:
@@ -391,30 +390,30 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- Now instead of checking out the remote git repository, the local over-
- ride will be used. Similar to a path source, every time the local git
- repository change, changes will be automatically picked up by Bundler.
- This means a commit in the local git repo will update the revision in
+ Now instead of checking out the remote git repository, the local over-
+ ride will be used. Similar to a path source, every time the local git
+ repository change, changes will be automatically picked up by Bundler.
+ This means a commit in the local git repo will update the revision in
the 1mGemfile.lock 22mto the local git repo revision. This requires the same
- attention as git submodules. Before pushing to the remote, you need to
+ attention as git submodules. Before pushing to the remote, you need to
ensure the local override was pushed, otherwise you may point to a com-
- mit that only exists in your local machine. You'll also need to CGI
- escape your usernames and passwords as well.
-
- Bundler does many checks to ensure a developer won't work with invalid
- references. Particularly, we force a developer to specify a branch in
- the 1mGemfile 22min order to use this feature. If the branch specified in
- the 1mGemfile 22mand the current branch in the local git repository do not
- match, Bundler will abort. This ensures that a developer is always
- working against the correct branches, and prevents accidental locking
+ mit that only exists in your local machine. You'll also need to CGI es-
+ cape your usernames and passwords as well.
+
+ Bundler does many checks to ensure a developer won't work with invalid
+ references. Particularly, we force a developer to specify a branch in
+ the 1mGemfile 22min order to use this feature. If the branch specified in
+ the 1mGemfile 22mand the current branch in the local git repository do not
+ match, Bundler will abort. This ensures that a developer is always
+ working against the correct branches, and prevents accidental locking
to a different branch.
- Finally, Bundler also ensures that the current revision in the 1mGem-0m
- 1mfile.lock 22mexists in the local git repository. By doing this, Bundler
+ Finally, Bundler also ensures that the current revision in the 1mGem-0m
+ 1mfile.lock 22mexists in the local git repository. By doing this, Bundler
forces you to fetch the latest changes in the remotes.
1mMIRRORS OF GEM SOURCES0m
- Bundler supports overriding gem sources with mirrors. This allows you
+ Bundler supports overriding gem sources with mirrors. This allows you
to configure rubygems.org as the gem source in your Gemfile while still
using your mirror to fetch gems.
@@ -424,7 +423,7 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- For example, to use a mirror of rubygems.org hosted at rubygems-mir-
+ For example, to use a mirror of rubygems.org hosted at rubygems-mir-
ror.org:
@@ -433,8 +432,8 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- Each mirror also provides a fallback timeout setting. If the mirror
- does not respond within the fallback timeout, Bundler will try to use
+ Each mirror also provides a fallback timeout setting. If the mirror
+ does not respond within the fallback timeout, Bundler will try to use
the original server instead of the mirror.
@@ -451,11 +450,11 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- The default fallback timeout is 0.1 seconds, but the setting can cur-
+ The default fallback timeout is 0.1 seconds, but the setting can cur-
rently only accept whole seconds (for example, 1, 15, or 30).
1mCREDENTIALS FOR GEM SOURCES0m
- Bundler allows you to configure credentials for any gem source, which
+ Bundler allows you to configure credentials for any gem source, which
allows you to avoid putting secrets into your Gemfile.
@@ -464,7 +463,7 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- For example, to save the credentials of user 1mclaudette 22mfor the gem
+ For example, to save the credentials of user 1mclaudette 22mfor the gem
source at 1mgems.longerous.com22m, you would run:
@@ -498,7 +497,7 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- This is especially useful for private repositories on hosts such as
+ This is especially useful for private repositories on hosts such as
Github, where you can use personal OAuth tokens:
@@ -508,9 +507,9 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
1mCONFIGURE BUNDLER DIRECTORIES0m
- Bundler's home, config, cache and plugin directories are able to be
- configured through environment variables. The default location for
- Bundler's home directory is 1m~/.bundle22m, which all directories inherit
+ Bundler's home, config, cache and plugin directories are able to be
+ configured through environment variables. The default location for
+ Bundler's home directory is 1m~/.bundle22m, which all directories inherit
from by default. The following outlines the available environment vari-
ables and their default values
@@ -526,4 +525,4 @@ BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
- December 2018 BUNDLE-CONFIG(1)
+ January 2019 BUNDLE-CONFIG(1)
diff --git a/man/bundle-exec.1.txt b/man/bundle-exec.1.txt
index fa55d2a0c2..864eb0b485 100644
--- a/man/bundle-exec.1.txt
+++ b/man/bundle-exec.1.txt
@@ -14,8 +14,8 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
Essentially, if you would normally have run something like 1mrspec0m
1mspec/my_spec.rb22m, and you want to use the gems specified in the [1mGem-0m
- 1mfile(5)22m][Gemfile(5)] and installed via bundle install(1) 4mbun-0m
- 4mdle-install.1.html24m, you should run 1mbundle exec rspec spec/my_spec.rb22m.
+ 1mfile(5)22m][Gemfile(5)] and installed via bundle install(1) 4mbundle-in-0m
+ 4mstall.1.html24m, you should run 1mbundle exec rspec spec/my_spec.rb22m.
Note that 1mbundle exec 22mdoes not require that an executable is available
on your shell's 1m$PATH22m.
@@ -27,10 +27,10 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
of passing all file descriptors to the new process.
1mBUNDLE INSTALL --BINSTUBS0m
- If you use the 1m--binstubs 22mflag in bundle install(1) 4mbun-0m
- 4mdle-install.1.html24m, Bundler will automatically create a directory
- (which defaults to 1mapp_root/bin22m) containing all of the executables
- available from gems in the bundle.
+ If you use the 1m--binstubs 22mflag in bundle install(1) 4mbundle-in-0m
+ 4mstall.1.html24m, Bundler will automatically create a directory (which de-
+ faults to 1mapp_root/bin22m) containing all of the executables available
+ from gems in the bundle.
After using 1m--binstubs22m, 1mbin/rspec spec/my_spec.rb 22mis identical to 1mbun-0m
1mdle exec rspec spec/my_spec.rb22m.
@@ -39,8 +39,8 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
1mbundle exec 22mmakes a number of changes to the shell environment, then
executes the command you specify in full.
- o make sure that it's still possible to shell out to 1mbundle 22mfrom
- inside a command invoked by 1mbundle exec 22m(using 1m$BUNDLE_BIN_PATH22m)
+ o make sure that it's still possible to shell out to 1mbundle 22mfrom in-
+ side a command invoked by 1mbundle exec 22m(using 1m$BUNDLE_BIN_PATH22m)
o put the directory containing executables (like 1mrails22m, 1mrspec22m,
1mrackup22m) for your bundle on 1m$PATH0m
@@ -82,18 +82,18 @@ BUNDLE-EXEC(1) BUNDLE-EXEC(1)
By default, when attempting to 1mbundle exec 22mto a file with a ruby she-
bang, Bundler will 1mKernel.load 22mthat file instead of using 1mKernel.exec22m.
For the vast majority of cases, this is a performance improvement. In a
- rare few cases, this could cause some subtle side-effects (such as
- dependence on the exact contents of 1m$0 22mor 1m__FILE__22m) and the optimiza-
- tion can be disabled by enabling the 1mdisable_exec_load 22msetting.
+ rare few cases, this could cause some subtle side-effects (such as de-
+ pendence on the exact contents of 1m$0 22mor 1m__FILE__22m) and the optimization
+ can be disabled by enabling the 1mdisable_exec_load 22msetting.
1mShelling out0m
Any Ruby code that opens a subshell (like 1msystem22m, backticks, or 1m%x{}22m)
will automatically use the current Bundler environment. If you need to
shell out to a Ruby command that is not part of your current bundle,
- use the 1mwith_clean_env 22mmethod with a block. Any subshells created
- inside the block will be given the environment present before Bundler
- was activated. For example, Homebrew commands run Ruby, but don't work
- inside a bundle:
+ use the 1mwith_clean_env 22mmethod with a block. Any subshells created in-
+ side the block will be given the environment present before Bundler was
+ activated. For example, Homebrew commands run Ruby, but don't work in-
+ side a bundle:
diff --git a/man/bundle-gem.1.txt b/man/bundle-gem.1.txt
index 59e5e0ddcc..a951d5b4b6 100644
--- a/man/bundle-gem.1.txt
+++ b/man/bundle-gem.1.txt
@@ -16,8 +16,8 @@ BUNDLE-GEM(1) BUNDLE-GEM(1)
Run 1mrake -T 22min the resulting project for a list of Rake tasks that can
be used to test and publish the gem to rubygems.org.
- The generated project skeleton can be customized with OPTIONS, as
- explained below. Note that these options can also be specified via
+ The generated project skeleton can be customized with OPTIONS, as ex-
+ plained below. Note that these options can also be specified via
Bundler's global configuration file using the following names:
o 1mgem.coc0m
@@ -57,9 +57,9 @@ BUNDLE-GEM(1) BUNDLE-GEM(1)
1m--mit 22mAdd an MIT license to a 1mLICENSE.txt 22mfile in the root of the gen-
erated project. Your name from the global git config is used for
- the copyright statement. If this option is unspecified, an
- interactive prompt will be displayed and the answer will be
- saved in Bundler's global config for future 1mbundle gem 22muse.
+ the copyright statement. If this option is unspecified, an in-
+ teractive prompt will be displayed and the answer will be saved
+ in Bundler's global config for future 1mbundle gem 22muse.
1m--no-mit0m
Do not create a 1mLICENSE.txt 22m(overrides 1m--mit 22mspecified in the
@@ -68,12 +68,12 @@ BUNDLE-GEM(1) BUNDLE-GEM(1)
1m-t22m, 1m--test=minitest22m, 1m--test=rspec0m
Specify the test framework that Bundler should use when generat-
ing the project. Acceptable values are 1mminitest 22mand 1mrspec22m. The
- 1mGEM_NAME.gemspec 22mwill be configured and a skeleton test/spec
- directory will be created based on this option. If this option
- is unspecified, an interactive prompt will be displayed and the
- answer will be saved in Bundler's global config for future 1mbun-0m
- 1mdle gem 22muse. If no option is specified, the default testing
- framework is RSpec.
+ 1mGEM_NAME.gemspec 22mwill be configured and a skeleton test/spec di-
+ rectory will be created based on this option. If this option is
+ unspecified, an interactive prompt will be displayed and the an-
+ swer will be saved in Bundler's global config for future 1mbundle0m
+ 1mgem 22muse. If no option is specified, the default testing frame-
+ work is RSpec.
1m-e22m, 1m--edit[=EDITOR]0m
Open the resulting GEM_NAME.gemspec in EDITOR, or the default
diff --git a/man/bundle-install.1 b/man/bundle-install.1
index c70f92eb25..8bd0a7fa3d 100644
--- a/man/bundle-install.1
+++ b/man/bundle-install.1
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "BUNDLE\-INSTALL" "1" "December 2018" "" ""
+.TH "BUNDLE\-INSTALL" "1" "January 2019" "" ""
.
.SH "NAME"
\fBbundle\-install\fR \- Install the dependencies specified in your Gemfile
diff --git a/man/bundle-install.1.txt b/man/bundle-install.1.txt
index 93118629c7..7637aeb8b7 100644
--- a/man/bundle-install.1.txt
+++ b/man/bundle-install.1.txt
@@ -39,8 +39,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
text. If used, you might add this directory to your environ-
ment's 1mPATH 22mvariable. For instance, if the 1mrails 22mgem comes with
a 1mrails 22mexecutable, this flag will create a 1mbin/rails 22mexecutable
- that ensures that all referred dependencies will be resolved
- using the bundled gems.
+ that ensures that all referred dependencies will be resolved us-
+ ing the bundled gems.
1m--clean0m
On finishing the installation Bundler is going to remove any
@@ -53,9 +53,9 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
this option enabled in your development environment.
1m--force0m
- Force download every gem, even if the required versions are
- already available locally. 1m--redownload 22mis an alias of this
- option.
+ Force download every gem, even if the required versions are al-
+ ready available locally. 1m--redownload 22mis an alias of this op-
+ tion.
1m--frozen0m
Do not allow the Gemfile.lock to be updated after this install.
@@ -82,8 +82,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
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.
+ 1mdor/cache22m. Note that if a appropriate platform-specific gem ex-
+ ists on 1mrubygems.org 22mit will not be found.
1m--no-cache0m
Do not update the cache in 1mvendor/cache 22mwith the newly bundled
@@ -103,8 +103,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
will not get listed.
1m--quiet0m
- Do not print progress information to the standard output.
- Instead, Bundler will exit using a status code (1m$?22m).
+ Do not print progress information to the standard output. In-
+ stead, Bundler will exit using a status code (1m$?22m).
1m--retry=[<number>]0m
Retry failed network or git requests for 4mnumber24m times.
@@ -155,8 +155,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
1. A 1mGemfile.lock 22mis required.
To ensure that the same versions of the gems you developed with and
- tested with are also used in deployments, a 1mGemfile.lock 22mis
- required.
+ tested with are also used in deployments, a 1mGemfile.lock 22mis re-
+ quired.
This is mainly to ensure that you remember to check your 1mGem-0m
1mfile.lock 22minto version control.
@@ -172,18 +172,18 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
3. Gems are installed to 1mvendor/bundle 22mnot your default system loca-
tion
- In development, it's convenient to share the gems used in your
- application with other applications and other scripts that run on
- the system.
+ In development, it's convenient to share the gems used in your ap-
+ plication with other applications and other scripts that run on the
+ system.
In deployment, isolation is a more important default. In addition,
- the user deploying the application may not have permission to
- install gems to the system, or the web server may not have permis-
- sion to read them.
+ the user deploying the application may not have permission to in-
+ stall gems to the system, or the web server may not have permission
+ to read them.
As a result, 1mbundle install --deployment 22minstalls gems to the 1mven-0m
- 1mdor/bundle 22mdirectory in the application. This may be overridden
- using the 1m--path 22moption.
+ 1mdor/bundle 22mdirectory in the application. This may be overridden us-
+ ing the 1m--path 22moption.
@@ -195,8 +195,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
ask you for your 1msudo 22mpassword in order to copy the gems into their
system location.
- From your perspective, this is identical to installing the gems
- directly into the system.
+ From your perspective, this is identical to installing the gems di-
+ rectly into the system.
You should never use 1msudo bundle install22m. This is because several other
steps in 1mbundle install 22mmust be performed as the current user:
@@ -265,9 +265,9 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
APIs unavailable in Rack 1.x, only to have Bundler switch to Rack 1.2
when the 1mproduction 22mgroup 4mis24m used.
- This should not cause any problems in practice, because we do not
- attempt to 1minstall 22mthe gems in the excluded groups, and only evaluate
- as part of the dependency resolution process.
+ This should not cause any problems in practice, because we do not at-
+ tempt to 1minstall 22mthe gems in the excluded groups, and only evaluate as
+ part of the dependency resolution process.
This also means that you cannot include different versions of the same
gem in different groups, because doing so would result in different
@@ -300,8 +300,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
When Bundler first shipped, the 1mGemfile.lock 22mwas included in the 1m.git-0m
1mignore 22mfile included with generated gems. Over time, however, it became
clear that this practice forces the pain of broken dependencies onto
- new contributors, while leaving existing contributors potentially
- unaware of the problem. Since 1mbundle install 22mis usually the first step
+ new contributors, while leaving existing contributors potentially un-
+ aware of the problem. Since 1mbundle install 22mis usually the first step
towards a contribution, the pain of broken dependencies would discour-
age new contributors from contributing. As a result, we have revised
our guidance for gem authors to now recommend checking in the lock for
@@ -331,8 +331,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
1m1.1.022m, while the 1mactivemerchant 22mgem depends on 1mactivesupport >= 2.3.222m,
1mbraintree >= 2.0.022m, and 1mbuilder >= 2.0.022m.
- When the dependencies are first resolved, Bundler will select
- 1mactivesupport 2.3.822m, which satisfies the requirements of both gems in
+ When the dependencies are first resolved, Bundler will select 1mac-0m
+ 1mtivesupport 2.3.822m, which satisfies the requirements of both gems in
your Gemfile(5).
Next, you modify your Gemfile(5) to:
@@ -346,12 +346,12 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
- The 1mactionpack 3.0.0.rc 22mgem has a number of new dependencies, and
- updates the 1mactivesupport 22mdependency to 1m= 3.0.0.rc 22mand the 1mrack 22mdepen-
+ The 1mactionpack 3.0.0.rc 22mgem has a number of new dependencies, and up-
+ dates the 1mactivesupport 22mdependency to 1m= 3.0.0.rc 22mand the 1mrack 22mdepen-
dency to 1m~> 1.2.122m.
- When you run 1mbundle install22m, Bundler notices that you changed the
- 1mactionpack 22mgem, but not the 1mactivemerchant 22mgem. It evaluates the gems
+ When you run 1mbundle install22m, Bundler notices that you changed the 1mac-0m
+ 1mtionpack 22mgem, but not the 1mactivemerchant 22mgem. It evaluates the gems
currently being used to satisfy its requirements:
1mactivesupport 2.3.80m
@@ -370,8 +370,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
retically matches 1mactivesupport 3.0.0.rc22m, Bundler treats gems in your
Gemfile(5) that have not changed as an atomic unit together with their
dependencies. In this case, the 1mactivemerchant 22mdependency is treated as
- 1mactivemerchant 1.7.1 + activesupport 2.3.822m, so 1mbundle install 22mwill
- report that it cannot update 1mactionpack22m.
+ 1mactivemerchant 1.7.1 + activesupport 2.3.822m, so 1mbundle install 22mwill re-
+ port that it cannot update 1mactionpack22m.
To explicitly update 1mactionpack22m, including its dependencies which other
gems in the Gemfile(5) still depend on, run 1mbundle update actionpack0m
@@ -383,8 +383,8 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
work, run bundle update(1) 4mbundle-update.1.html24m.
1mSEE ALSO0m
- o Gem install docs
- 4mhttp://guides.rubygems.org/rubygems-basics/#installing-gems0m
+ o Gem install docs 4mhttp://guides.rubygems.org/rubygems-basics/#in-0m
+ 4mstalling-gems0m
o Rubygems signing docs 4mhttp://guides.rubygems.org/security/0m
@@ -393,4 +393,4 @@ BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
- December 2018 BUNDLE-INSTALL(1)
+ January 2019 BUNDLE-INSTALL(1)
diff --git a/man/bundle-lock.1.txt b/man/bundle-lock.1.txt
index 2c757f0201..838c1baae5 100644
--- a/man/bundle-lock.1.txt
+++ b/man/bundle-lock.1.txt
@@ -21,8 +21,8 @@ BUNDLE-LOCK(1) BUNDLE-LOCK(1)
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.
+ 1mdor/cache22m. Note that if a appropriate platform-specific gem ex-
+ ists on 1mrubygems.org 22mit will not be found.
1m--print0m
Prints the lockfile to STDOUT instead of writing to the file
@@ -60,17 +60,17 @@ BUNDLE-LOCK(1) BUNDLE-LOCK(1)
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
- in the sources.
+ bundler will ignore any previously installed gems and resolve all de-
+ pendencies again based on the latest versions of all gems available in
+ the sources.
1mUPDATING A LIST OF GEMS0m
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.
- For instance, you only want to update 1mnokogiri22m, run 1mbundle lock0m
- 1m--update nokogiri22m.
+ For instance, you only want to update 1mnokogiri22m, run 1mbundle lock --up-0m
+ 1mdate nokogiri22m.
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
diff --git a/man/bundle-outdated.1.txt b/man/bundle-outdated.1.txt
index 00779962fc..dc9d7a06c7 100644
--- a/man/bundle-outdated.1.txt
+++ b/man/bundle-outdated.1.txt
@@ -7,9 +7,9 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
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] [--only-explicit]
+ [--parseable | --porcelain] [--group=GROUP] [--groups] [--up-
+ date-strict] [--patch|--minor|--major] [--filter-major] [--filter-mi-
+ nor] [--filter-patch] [--only-explicit]
1mDESCRIPTION0m
Outdated lists the names and versions of gems that have a newer version
@@ -20,8 +20,8 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
1mOPTIONS0m
1m--local0m
- Do not attempt to fetch gems remotely and use the gem cache
- instead.
+ Do not attempt to fetch gems remotely and use the gem cache in-
+ stead.
1m--pre 22mCheck for newer pre-release gems.
@@ -41,8 +41,8 @@ BUNDLE-OUTDATED(1) BUNDLE-OUTDATED(1)
List gems organized by groups.
1m--update-strict0m
- Strict conservative resolution, do not allow any gem to be
- updated past latest --patch | --minor| --major.
+ Strict conservative resolution, do not allow any gem to be up-
+ dated past latest --patch | --minor| --major.
1m--minor0m
Prefer updating only to next minor version.
diff --git a/man/bundle-package.1.txt b/man/bundle-package.1.txt
index e581e94507..56b977f0ca 100644
--- a/man/bundle-package.1.txt
+++ b/man/bundle-package.1.txt
@@ -10,15 +10,15 @@ BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)
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
+ 1mdor/cache 22mdirectory. In the future, when running [bundle in-
+ stall(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.
+ 1m:path 22mdependencies besides .gem files. This needs to be explicitly en-
+ abled via the 1m--all 22moption. Once used, the 1m--all 22moption will be remem-
+ bered.
1mSUPPORT FOR MULTIPLE PLATFORMS0m
When using gems that have different packages for different platforms,
@@ -48,9 +48,9 @@ BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)
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
+ Even though the 1mnokogiri 22mgem for the Ruby platform is 4mtechnically24m ac-
+ ceptable 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.
diff --git a/man/bundle-pristine.1.txt b/man/bundle-pristine.1.txt
index a46f3c830c..2fd320282a 100644
--- a/man/bundle-pristine.1.txt
+++ b/man/bundle-pristine.1.txt
@@ -18,9 +18,9 @@ BUNDLE-PRISTINE(1) BUNDLE-PRISTINE(1)
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.
+ 1mpristine22m. One also cannot use 1mbundle pristine 22mon gems with a 'path' op-
+ tion in the Gemfile, because bundler has no original copy it can re-
+ store from.
When is it practical to use 1mbundle pristine22m?
diff --git a/man/bundle-remove.1.txt b/man/bundle-remove.1.txt
index 2cf2ba6010..5248a0ee18 100644
--- a/man/bundle-remove.1.txt
+++ b/man/bundle-remove.1.txt
@@ -17,8 +17,8 @@ BUNDLE-REMOVE(1) BUNDLE-REMOVE(1)
1mOPTIONS0m
1m--install0m
Runs 1mbundle install 22mafter 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
+ the Gemfile, which ensures that both the lockfile and the in-
+ stalled gems on disk are also updated to remove the given
gem(s).
Example:
diff --git a/man/bundle-update.1 b/man/bundle-update.1
index 1fe205cff0..513bc64905 100644
--- a/man/bundle-update.1
+++ b/man/bundle-update.1
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "BUNDLE\-UPDATE" "1" "December 2018" "" ""
+.TH "BUNDLE\-UPDATE" "1" "January 2019" "" ""
.
.SH "NAME"
\fBbundle\-update\fR \- Update your gems to the latest available versions
diff --git a/man/bundle-update.1.txt b/man/bundle-update.1.txt
index 1a206e2c49..d40b05485a 100644
--- a/man/bundle-update.1.txt
+++ b/man/bundle-update.1.txt
@@ -35,8 +35,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
1m--source rails0m
1m--local0m
- Do not attempt to fetch gems remotely and use the gem cache
- instead.
+ Do not attempt to fetch gems remotely and use the gem cache in-
+ stead.
1m--ruby 22mUpdate the locked version of Ruby to the current version of
Ruby.
@@ -79,8 +79,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
shared dependencies to be updated.
1mUPDATING ALL GEMS0m
- If you run 1mbundle update --all22m, bundler will ignore any previously
- installed gems and resolve all dependencies again based on the latest
+ If you run 1mbundle update --all22m, bundler will ignore any previously in-
+ stalled gems and resolve all dependencies again based on the latest
versions of all gems available in the sources.
Consider the following Gemfile(5):
@@ -95,8 +95,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
When you run bundle install(1) 4mbundle-install.1.html24m the first time,
- bundler will resolve all of the dependencies, all the way down, and
- install what you need:
+ bundler will resolve all of the dependencies, all the way down, and in-
+ stall what you need:
@@ -153,8 +153,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
To do this, run 1mbundle update --all22m, which will ignore the 1mGem-0m
1mfile.lock22m, and resolve all the dependencies again. Keep in mind that
this process can result in a significantly different set of the 25
- gems, based on the requirements of new gems that the gem authors
- released since the last time you ran 1mbundle update --all22m.
+ gems, based on the requirements of new gems that the gem authors re-
+ leased since the last time you ran 1mbundle update --all22m.
1mUPDATING A LIST OF GEMS0m
Sometimes, you want to update a single gem in the Gemfile(5), and leave
@@ -182,8 +182,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
- The 1mthin 22mgem depends on 1mrack >= 1.022m, while 1mrack-perftools-profiler0m
- depends on 1mrack ~> 1.022m. If you run bundle install, you get:
+ The 1mthin 22mgem depends on 1mrack >= 1.022m, while 1mrack-perftools-profiler 22mde-
+ pends on 1mrack ~> 1.022m. If you run bundle install, you get:
@@ -200,8 +200,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
In this case, the two gems have their own set of dependencies, but they
- share 1mrack 22min common. If you run 1mbundle update thin22m, bundler will
- update 1mdaemons22m, 1meventmachine 22mand 1mrack22m, which are dependencies of 1mthin22m,
+ share 1mrack 22min common. If you run 1mbundle update thin22m, bundler will up-
+ date 1mdaemons22m, 1meventmachine 22mand 1mrack22m, which are dependencies of 1mthin22m,
but not 1mopen4 22mor 1mperftools.rb22m, which are dependencies of
1mrack-perftools_profiler22m. Note that 1mbundle update thin 22mwill update 1mrack0m
even though it's 4malso24m a dependency of 1mrack-perftools_profiler22m.
@@ -215,10 +215,10 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
4mdle-install.1.html24m:
In this scenario, updating the 1mthin 22mversion manually in the Gemfile(5),
- and then running bundle install(1) 4mbundle-install.1.html24m will only
- update 1mdaemons 22mand 1meventmachine22m, but not 1mrack22m. For more information,
- see the 1mCONSERVATIVE UPDATING 22msection of bundle install(1) 4mbun-0m
- 4mdle-install.1.html24m.
+ and then running bundle install(1) 4mbundle-install.1.html24m will only up-
+ date 1mdaemons 22mand 1meventmachine22m, but not 1mrack22m. For more information, see
+ the 1mCONSERVATIVE UPDATING 22msection of bundle install(1) 4mbundle-in-0m
+ 4mstall.1.html24m.
Starting with 1.14, specifying the 1m--conservative 22moption will also pre-
vent shared dependencies from being updated.
@@ -242,11 +242,11 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
Do not allow any gem to be updated past latest 1m--patch 22m| 1m--minor0m
| 1m--major22m.
- When Bundler is resolving what versions to use to satisfy declared
- requirements in the Gemfile or in parent gems, it looks up all avail-
- able versions, filters out any versions that don't satisfy the require-
- ment, and then, by default, sorts them from newest to oldest, consider-
- ing them in that order.
+ When Bundler is resolving what versions to use to satisfy declared re-
+ quirements in the Gemfile or in parent gems, it looks up all available
+ versions, filters out any versions that don't satisfy the requirement,
+ and then, by default, sorts them from newest to oldest, considering
+ them in that order.
Providing one of the patch level options (e.g. 1m--patch22m) changes the
sort order of the satisfying versions, causing Bundler to consider the
@@ -266,16 +266,16 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
"1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0".
Combining the 1m--strict 22moption with any of the patch level options will
- remove any versions beyond the scope of the patch level option, to
- ensure that no gem is updated that far.
+ remove any versions beyond the scope of the patch level option, to en-
+ sure that no gem is updated that far.
To continue the previous example, if both 1m--patch 22mand 1m--strict 22moptions
are used, the available versions for resolution would be "1.0.4, 1.0.3,
1.0.2". If 1m--minor 22mand 1m--strict 22mare used, it would be "1.1.1, 1.1.0,
1.0.4, 1.0.3, 1.0.2".
- Gem requirements as defined in the Gemfile will still be the first
- determining factor for what versions are available. If the gem require-
+ Gem requirements as defined in the Gemfile will still be the first de-
+ termining factor for what versions are available. If the gem require-
ment for 1mfoo 22min the Gemfile is '~> 1.0', that will accomplish the same
thing as providing the 1m--minor 22mand 1m--strict 22moptions.
@@ -328,8 +328,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
In case 1, bar is upgraded to 2.1.1, a minor version increase, because
the dependency from foo 1.4.5 required it.
- In case 2, only foo is requested to be unlocked, but bar is also
- allowed to move because it's not a declared dependency in the Gemfile.
+ In case 2, only foo is requested to be unlocked, but bar is also al-
+ lowed to move because it's not a declared dependency in the Gemfile.
In case 3, bar goes up a whole major release, because a minor increase
is preferred now for foo, and when it goes to 1.5.1, it requires 3.0.0
@@ -388,4 +388,4 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
- December 2018 BUNDLE-UPDATE(1)
+ January 2019 BUNDLE-UPDATE(1)
diff --git a/man/bundle.1 b/man/bundle.1
index abb90154d9..cc777c9aab 100644
--- a/man/bundle.1
+++ b/man/bundle.1
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "BUNDLE" "1" "November 2018" "" ""
+.TH "BUNDLE" "1" "January 2019" "" ""
.
.SH "NAME"
\fBbundle\fR \- Ruby Dependency Management
@@ -116,6 +116,10 @@ Clean up unused gems in your Bundler directory
\fBbundle doctor(1)\fR \fIbundle\-doctor\.1\.html\fR
Display warnings about common problems
.
+.TP
+\fBbundle remove(1)\fR \fIbundle\-remove\.1\.html\fR
+Removes gems from the Gemfile
+.
.SH "PLUGINS"
When running a command that isn\'t listed in PRIMARY COMMANDS or UTILITIES, Bundler will try to find an executable on your path named \fBbundler\-<command>\fR and execute it, passing down any extra arguments to it\.
.
diff --git a/man/bundle.1.txt b/man/bundle.1.txt
index 0f38628621..751411846f 100644
--- a/man/bundle.1.txt
+++ b/man/bundle.1.txt
@@ -56,8 +56,8 @@ BUNDLE(1) BUNDLE(1)
Generate binstubs for executables in a gem
1mbundle check(1) 4m22mbundle-check.1.html0m
- Determine whether the requirements for your application are
- installed and available to Bundler
+ Determine whether the requirements for your application are in-
+ stalled and available to Bundler
1mbundle show(1) 4m22mbundle-show.1.html0m
Show the source location of a particular gem in the bundle
@@ -92,6 +92,9 @@ BUNDLE(1) BUNDLE(1)
1mbundle doctor(1) 4m22mbundle-doctor.1.html0m
Display warnings about common problems
+ 1mbundle remove(1) 4m22mbundle-remove.1.html0m
+ Removes gems from the Gemfile
+
1mPLUGINS0m
When running a command that isn't listed in PRIMARY COMMANDS or UTILI-
TIES, Bundler will try to find an executable on your path named
@@ -110,4 +113,4 @@ BUNDLE(1) BUNDLE(1)
- November 2018 BUNDLE(1)
+ January 2019 BUNDLE(1)
diff --git a/man/bundle.ronn b/man/bundle.ronn
index c03201a30c..0005692abd 100644
--- a/man/bundle.ronn
+++ b/man/bundle.ronn
@@ -94,6 +94,9 @@ We divide `bundle` subcommands into primary commands and utilities:
* [`bundle doctor(1)`](bundle-doctor.1.html):
Display warnings about common problems
+* [`bundle remove(1)`](bundle-remove.1.html):
+ Removes gems from the Gemfile
+
## PLUGINS
When running a command that isn't listed in PRIMARY COMMANDS or UTILITIES,
diff --git a/man/gemfile.5 b/man/gemfile.5
index ccb258f50f..c40ad9c71b 100644
--- a/man/gemfile.5
+++ b/man/gemfile.5
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "GEMFILE" "5" "November 2018" "" ""
+.TH "GEMFILE" "5" "January 2019" "" ""
.
.SH "NAME"
\fBGemfile\fR \- A format for describing gem dependencies for Ruby programs
@@ -299,19 +299,19 @@ The full list of platforms and supported versions includes:
.
.TP
\fBruby\fR
-1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5
+1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6
.
.TP
\fBmri\fR
-1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5
+1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6
.
.TP
\fBmingw\fR
-1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5
+1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6
.
.TP
\fBx64_mingw\fR
-2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5
+2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6
.
.P
As with groups, you can specify one or more platforms:
diff --git a/man/gemfile.5.ronn b/man/gemfile.5.ronn
index f4772f6d8d..c941463edc 100644
--- a/man/gemfile.5.ronn
+++ b/man/gemfile.5.ronn
@@ -216,13 +216,13 @@ used on platforms with Ruby 2.3, use:
The full list of platforms and supported versions includes:
* `ruby`:
- 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
* `mri`:
- 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
* `mingw`:
- 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
* `x64_mingw`:
- 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
As with groups, you can specify one or more platforms:
diff --git a/man/gemfile.5.txt b/man/gemfile.5.txt
index 85ef7135d9..0a01c045d7 100644
--- a/man/gemfile.5.txt
+++ b/man/gemfile.5.txt
@@ -43,8 +43,8 @@ GEMFILE(5) GEMFILE(5)
Some gem sources require a username and password. Use bundle config(1)
4mbundle-config.1.html24m to set the username and password for any of the
sources that need it. The command must be run once on each computer
- that will install the Gemfile, but this keeps the credentials from
- being stored in plain text in version control.
+ that will install the Gemfile, but this keeps the credentials from be-
+ ing stored in plain text in version control.
@@ -98,8 +98,8 @@ GEMFILE(5) GEMFILE(5)
o Other implementations 4mhttps://www.ruby-lang.org/en/about/24m of Ruby
exist. Some of the more well-known implementations include Rubinius
4mhttps://rubinius.com/24m, and JRuby 4mhttp://jruby.org/24m. Rubinius is an
- alternative implementation of Ruby written in Ruby. JRuby is an
- implementation of Ruby on the JVM, short for Java Virtual Machine.
+ alternative implementation of Ruby written in Ruby. JRuby is an im-
+ plementation of Ruby on the JVM, short for Java Virtual Machine.
@@ -227,8 +227,8 @@ GEMFILE(5) GEMFILE(5)
Note that on 1mbundle install22m, bundler downloads and evaluates all gems,
in order to create a single canonical list of all of the required gems
and their dependencies. This means that you cannot list different ver-
- sions of the same gems in different groups. For more details, see
- Understanding Bundler 4mhttp://bundler.io/rationale.html24m.
+ sions of the same gems in different groups. For more details, see Un-
+ derstanding Bundler 4mhttp://bundler.io/rationale.html24m.
1mPLATFORMS0m
If a gem should only be used in a particular platform or set of plat-
@@ -256,8 +256,8 @@ GEMFILE(5) GEMFILE(5)
1mmswin 22mWindows
- You can restrict further by platform and version for all platforms
- 4mexcept24m for 1mrbx22m, 1mjruby22m, 1mtruffleruby 22mand 1mmswin22m.
+ You can restrict further by platform and version for all platforms 4mex-0m
+ 4mcept24m for 1mrbx22m, 1mjruby22m, 1mtruffleruby 22mand 1mmswin22m.
To specify a version in addition to a platform, append the version num-
ber without the delimiter to the platform. For example, to specify that
@@ -271,14 +271,14 @@ GEMFILE(5) GEMFILE(5)
The full list of platforms and supported versions includes:
- 1mruby 22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 1mruby 22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
- 1mmri 22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 1mmri 22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
- 1mmingw 22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 1mmingw 22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
1mx64_mingw0m
- 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+ 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
As with groups, you can specify one or more platforms:
@@ -313,8 +313,8 @@ GEMFILE(5) GEMFILE(5)
it will fall back on global sources using the ordering described in
4mSOURCE24m 4mPRIORITY24m.
- Selecting a specific source repository this way also suppresses the
- ambiguous gem warning described above in 4mGLOBAL24m 4mSOURCES24m 4m(#source)24m.
+ Selecting a specific source repository this way also suppresses the am-
+ biguous gem warning described above in 4mGLOBAL24m 4mSOURCES24m 4m(#source)24m.
Using the 1m:source 22moption for an individual gem will also make that
source available as a possible global source for any other gems which
@@ -342,13 +342,13 @@ GEMFILE(5) GEMFILE(5)
can deliver malicious code and compromise your system. HTTPS and SSH
are strongly preferred.
- The 1mgroup22m, 1mplatforms22m, and 1mrequire 22moptions are available and behave
- exactly the same as they would for a normal gem.
+ The 1mgroup22m, 1mplatforms22m, and 1mrequire 22moptions are available and behave ex-
+ actly the same as they would for a normal gem.
- A git repository 1mSHOULD 22mhave at least one file, at the root of the
- directory containing the gem, with the extension 1m.gemspec22m. This file
- 1mMUST 22mcontain a valid gem specification, as expected by the 1mgem build0m
- command.
+ A git repository 1mSHOULD 22mhave at least one file, at the root of the di-
+ rectory containing the gem, with the extension 1m.gemspec22m. This file 1mMUST0m
+ contain a valid gem specification, as expected by the 1mgem build 22mcom-
+ mand.
If a git repository does not have a 1m.gemspec22m, bundler will attempt to
create one, but it will not contain any dependencies, executables, or C
@@ -419,8 +419,8 @@ GEMFILE(5) GEMFILE(5)
1mGIT SOURCE0m
A custom git source can be defined via the 1mgit_source 22mmethod. Provide
the source's name as an argument, and a block which receives a single
- argument and interpolates it into a string to return the full repo
- address:
+ argument and interpolates it into a string to return the full repo ad-
+ dress:
@@ -510,8 +510,8 @@ GEMFILE(5) GEMFILE(5)
- Since the 1mbitbucket 22mmethod is a specialization of 1mgit_source22m, it
- accepts a 1m:branch 22mnamed argument.
+ Since the 1mbitbucket 22mmethod is a specialization of 1mgit_source22m, it ac-
+ cepts a 1m:branch 22mnamed argument.
1mPATH0m
You can specify that a gem is located in a particular location on the
@@ -573,8 +573,8 @@ GEMFILE(5) GEMFILE(5)
In the case of the group block form the :optional option can be given
- to prevent a group from being installed unless listed in the 1m--with0m
- option given to the 1mbundle install 22mcommand.
+ to prevent a group from being installed unless listed in the 1m--with 22mop-
+ tion given to the 1mbundle install 22mcommand.
In the case of the 1mgit 22mblock form, the 1m:ref22m, 1m:branch22m, 1m:tag22m, and 1m:sub-0m
1mmodules 22moptions may be passed to the 1mgit 22mmethod, and all gems in the
@@ -584,8 +584,8 @@ GEMFILE(5) GEMFILE(5)
available as a possible global source for any other gems which do not
specify explicit sources. Thus, when defining source blocks, it is rec-
ommended that you also ensure all other gems in the Gemfile are using
- explicit sources, either via source blocks or 1m:source 22mdirectives on
- individual gems.
+ explicit sources, either via source blocks or 1m:source 22mdirectives on in-
+ dividual gems.
1mINSTALL_IF0m
The 1minstall_if 22mmethod allows gems to be installed based on a proc or
@@ -612,12 +612,12 @@ GEMFILE(5) GEMFILE(5)
cies listed in the 1m.gemspec 22mfile.
The 1mgemspec 22mmethod adds any runtime dependencies as gem requirements in
- the default group. It also adds development dependencies as gem
- requirements in the 1mdevelopment 22mgroup. Finally, it adds a gem require-
- ment on your project (1m:path => '.'22m). In conjunction with 1mBundler.setup22m,
- this allows you to require project files in your test code as you would
- if the project were installed as a gem; you need not manipulate the
- load path manually or require project files via relative paths.
+ the default group. It also adds development dependencies as gem re-
+ quirements in the 1mdevelopment 22mgroup. Finally, it adds a gem requirement
+ on your project (1m:path => '.'22m). In conjunction with 1mBundler.setup22m, this
+ allows you to require project files in your test code as you would if
+ the project were installed as a gem; you need not manipulate the load
+ path manually or require project files via relative paths.
The 1mgemspec 22mmethod supports optional 1m:path22m, 1m:glob22m, 1m:name22m, and 1m:develop-0m
1mment_group 22moptions, which control where bundler looks for the 1m.gemspec22m,
@@ -650,4 +650,4 @@ GEMFILE(5) GEMFILE(5)
- November 2018 GEMFILE(5)
+ January 2019 GEMFILE(5)
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-26 02:31:41 +0000