bundler 1.9.0 → 1.17.3
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of bundler might be problematic. Click here for more details.
- checksums.yaml +5 -5
- data/CHANGELOG.md +1157 -6
- data/README.md +33 -6
- data/bundler.gemspec +51 -18
- data/exe/bundle +31 -0
- data/{bin → exe}/bundle_ruby +10 -6
- data/exe/bundler +4 -0
- data/lib/bundler.rb +326 -207
- data/lib/bundler/build_metadata.rb +53 -0
- data/lib/bundler/capistrano.rb +9 -3
- data/lib/bundler/cli.rb +522 -141
- data/lib/bundler/cli/add.rb +35 -0
- data/lib/bundler/cli/binstubs.rb +22 -11
- data/lib/bundler/cli/cache.rb +7 -6
- data/lib/bundler/cli/check.rb +11 -8
- data/lib/bundler/cli/clean.rb +7 -8
- data/lib/bundler/cli/common.rb +53 -7
- data/lib/bundler/cli/config.rb +84 -49
- data/lib/bundler/cli/console.rb +13 -8
- data/lib/bundler/cli/doctor.rb +140 -0
- data/lib/bundler/cli/exec.rb +77 -16
- data/lib/bundler/cli/gem.rb +120 -52
- data/lib/bundler/cli/info.rb +50 -0
- data/lib/bundler/cli/init.rb +21 -7
- data/lib/bundler/cli/inject.rb +37 -10
- data/lib/bundler/cli/install.rb +139 -78
- data/lib/bundler/cli/issue.rb +40 -0
- data/lib/bundler/cli/list.rb +58 -0
- data/lib/bundler/cli/lock.rb +63 -0
- data/lib/bundler/cli/open.rb +9 -6
- data/lib/bundler/cli/outdated.rb +221 -35
- data/lib/bundler/cli/package.rb +11 -7
- data/lib/bundler/cli/platform.rb +7 -4
- data/lib/bundler/cli/plugin.rb +24 -0
- data/lib/bundler/cli/pristine.rb +47 -0
- data/lib/bundler/cli/remove.rb +18 -0
- data/lib/bundler/cli/show.rb +11 -10
- data/lib/bundler/cli/update.rb +47 -29
- data/lib/bundler/cli/viz.rb +12 -8
- data/lib/bundler/compact_index_client.rb +109 -0
- data/lib/bundler/compact_index_client/cache.rb +118 -0
- data/lib/bundler/compact_index_client/updater.rb +116 -0
- data/lib/bundler/compatibility_guard.rb +14 -0
- data/lib/bundler/constants.rb +3 -1
- data/lib/bundler/current_ruby.rb +47 -137
- data/lib/bundler/definition.rb +599 -230
- data/lib/bundler/dep_proxy.rb +15 -10
- data/lib/bundler/dependency.rb +54 -25
- data/lib/bundler/deployment.rb +12 -2
- data/lib/bundler/deprecate.rb +33 -4
- data/lib/bundler/dsl.rb +383 -99
- data/lib/bundler/endpoint_specification.rb +72 -7
- data/lib/bundler/env.rb +121 -41
- data/lib/bundler/environment_preserver.rb +59 -0
- data/lib/bundler/errors.rb +158 -0
- data/lib/bundler/feature_flag.rb +74 -0
- data/lib/bundler/fetcher.rb +171 -280
- data/lib/bundler/fetcher/base.rb +52 -0
- data/lib/bundler/fetcher/compact_index.rb +126 -0
- data/lib/bundler/fetcher/dependency.rb +82 -0
- data/lib/bundler/fetcher/downloader.rb +84 -0
- data/lib/bundler/fetcher/index.rb +52 -0
- data/lib/bundler/friendly_errors.rb +113 -58
- data/lib/bundler/gem_helper.rb +73 -46
- data/lib/bundler/gem_helpers.rb +85 -9
- data/lib/bundler/gem_remote_fetcher.rb +43 -0
- data/lib/bundler/gem_tasks.rb +6 -1
- data/lib/bundler/gem_version_promoter.rb +190 -0
- data/lib/bundler/gemdeps.rb +29 -0
- data/lib/bundler/graph.rb +32 -49
- data/lib/bundler/index.rb +79 -67
- data/lib/bundler/injector.rb +219 -30
- data/lib/bundler/inline.rb +74 -0
- data/lib/bundler/installer.rb +191 -206
- data/lib/bundler/installer/gem_installer.rb +85 -0
- data/lib/bundler/installer/parallel_installer.rb +233 -0
- data/lib/bundler/installer/standalone.rb +53 -0
- data/lib/bundler/lazy_specification.rb +53 -13
- data/lib/bundler/lockfile_generator.rb +95 -0
- data/lib/bundler/lockfile_parser.rb +157 -62
- data/lib/bundler/match_platform.rb +15 -4
- data/lib/bundler/mirror.rb +223 -0
- data/lib/bundler/plugin.rb +292 -0
- data/lib/bundler/plugin/api.rb +81 -0
- data/lib/bundler/plugin/api/source.rb +306 -0
- data/lib/bundler/plugin/dsl.rb +53 -0
- data/lib/bundler/plugin/events.rb +61 -0
- data/lib/bundler/plugin/index.rb +162 -0
- data/lib/bundler/plugin/installer.rb +96 -0
- data/lib/bundler/plugin/installer/git.rb +38 -0
- data/lib/bundler/plugin/installer/rubygems.rb +27 -0
- data/lib/bundler/plugin/source_list.rb +27 -0
- data/lib/bundler/process_lock.rb +24 -0
- data/lib/bundler/psyched_yaml.rb +17 -6
- data/lib/bundler/remote_specification.rb +68 -11
- data/lib/bundler/resolver.rb +263 -229
- data/lib/bundler/resolver/spec_group.rb +106 -0
- data/lib/bundler/retry.rb +25 -19
- data/lib/bundler/ruby_dsl.rb +9 -2
- data/lib/bundler/ruby_version.rb +101 -66
- data/lib/bundler/rubygems_ext.rb +77 -37
- data/lib/bundler/rubygems_gem_installer.rb +106 -0
- data/lib/bundler/rubygems_integration.rb +450 -163
- data/lib/bundler/runtime.rb +133 -103
- data/lib/bundler/settings.rb +344 -83
- data/lib/bundler/settings/validator.rb +102 -0
- data/lib/bundler/setup.rb +7 -3
- data/lib/bundler/shared_helpers.rb +284 -54
- data/lib/bundler/similarity_detector.rb +21 -21
- data/lib/bundler/source.rb +68 -15
- data/lib/bundler/source/gemspec.rb +18 -0
- data/lib/bundler/source/git.rb +90 -55
- data/lib/bundler/source/git/git_proxy.rb +135 -35
- data/lib/bundler/source/metadata.rb +62 -0
- data/lib/bundler/source/path.rb +84 -61
- data/lib/bundler/source/path/installer.rb +53 -17
- data/lib/bundler/source/rubygems.rb +282 -122
- data/lib/bundler/source/rubygems/remote.rb +69 -0
- data/lib/bundler/source_list.rb +107 -22
- data/lib/bundler/spec_set.rb +83 -45
- data/lib/bundler/ssl_certs/certificate_manager.rb +8 -7
- data/lib/bundler/ssl_certs/index.rubygems.org/GlobalSignRootCA.pem +21 -0
- data/lib/bundler/ssl_certs/{DigiCertHighAssuranceEVRootCA.pem → rubygems.global.ssl.fastly.net/DigiCertHighAssuranceEVRootCA.pem} +0 -0
- data/lib/bundler/ssl_certs/{AddTrustExternalCARoot-2048.pem → rubygems.org/AddTrustExternalCARoot.pem} +0 -0
- data/lib/bundler/stub_specification.rb +108 -0
- data/lib/bundler/templates/.document +1 -0
- data/lib/bundler/templates/Executable +19 -6
- data/lib/bundler/templates/Executable.bundler +105 -0
- data/lib/bundler/templates/Executable.standalone +6 -4
- data/lib/bundler/templates/Gemfile +4 -1
- data/lib/bundler/templates/gems.rb +8 -0
- data/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt +68 -7
- data/lib/bundler/templates/newgem/Gemfile.tt +4 -2
- data/lib/bundler/templates/newgem/LICENSE.txt.tt +1 -1
- data/lib/bundler/templates/newgem/README.md.tt +19 -11
- data/lib/bundler/templates/newgem/Rakefile.tt +10 -6
- data/lib/bundler/templates/newgem/bin/console.tt +1 -1
- data/lib/bundler/templates/newgem/bin/setup.tt +2 -1
- data/lib/bundler/templates/newgem/ext/newgem/newgem.c.tt +4 -4
- data/lib/bundler/templates/newgem/ext/newgem/newgem.h.tt +3 -3
- data/lib/bundler/templates/newgem/gitignore.tt +5 -1
- data/lib/bundler/templates/newgem/lib/newgem.rb.tt +7 -6
- data/lib/bundler/templates/newgem/lib/newgem/version.rb.tt +4 -4
- data/lib/bundler/templates/newgem/newgem.gemspec.tt +31 -15
- data/lib/bundler/templates/newgem/rspec.tt +1 -0
- data/lib/bundler/templates/newgem/spec/newgem_spec.rb.tt +3 -5
- data/lib/bundler/templates/newgem/spec/spec_helper.rb.tt +14 -2
- data/lib/bundler/templates/newgem/test/{test_newgem.rb.tt → newgem_test.rb.tt} +2 -2
- data/lib/bundler/templates/newgem/test/test_helper.rb.tt +4 -0
- data/lib/bundler/templates/newgem/travis.yml.tt +7 -0
- data/lib/bundler/ui.rb +5 -3
- data/lib/bundler/ui/rg_proxy.rb +5 -7
- data/lib/bundler/ui/shell.rb +69 -18
- data/lib/bundler/ui/silent.rb +26 -1
- data/lib/bundler/uri_credentials_filter.rb +37 -0
- data/lib/bundler/vendor/fileutils/lib/fileutils.rb +1638 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo.rb +12 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/compatibility.rb +26 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/resolution_state.rb +57 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/specification_provider.rb +81 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph.rb +223 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/action.rb +36 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_edge_no_circular.rb +66 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_vertex.rb +62 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/delete_edge.rb +63 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/detach_vertex_named.rb +61 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/log.rb +126 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/set_payload.rb +46 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/tag.rb +36 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/vertex.rb +136 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/errors.rb +143 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/gem_metadata.rb +6 -0
- data/lib/bundler/vendor/{Molinillo-0.2.1 → molinillo}/lib/molinillo/modules/specification_provider.rb +11 -0
- data/lib/bundler/vendor/{Molinillo-0.2.1 → molinillo}/lib/molinillo/modules/ui.rb +6 -2
- data/lib/bundler/vendor/molinillo/lib/molinillo/resolution.rb +837 -0
- data/lib/bundler/vendor/{Molinillo-0.2.1 → molinillo}/lib/molinillo/resolver.rb +6 -3
- data/lib/bundler/vendor/molinillo/lib/molinillo/state.rb +58 -0
- data/lib/bundler/vendor/{net → net-http-persistent/lib/net}/http/faster.rb +1 -0
- data/lib/bundler/vendor/{net → net-http-persistent/lib/net}/http/persistent.rb +27 -24
- data/lib/bundler/vendor/{net → net-http-persistent/lib/net}/http/persistent/ssl_reuse.rb +2 -1
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor.rb +47 -22
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions.rb +31 -29
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions/create_file.rb +3 -2
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions/create_link.rb +3 -2
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions/directory.rb +3 -3
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions/empty_directory.rb +16 -8
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions/file_manipulation.rb +66 -18
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/actions/inject_into_file.rb +18 -16
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/base.rb +67 -44
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/command.rb +13 -11
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/core_ext/hash_with_indifferent_access.rb +21 -1
- data/lib/bundler/vendor/thor/lib/thor/core_ext/io_binary_read.rb +12 -0
- data/lib/bundler/vendor/thor/lib/thor/core_ext/ordered_hash.rb +129 -0
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/error.rb +3 -3
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/group.rb +14 -14
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/invocation.rb +4 -5
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/line_editor.rb +2 -2
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/line_editor/basic.rb +2 -0
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/line_editor/readline.rb +0 -0
- data/lib/bundler/vendor/thor/lib/thor/parser.rb +4 -0
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/parser/argument.rb +4 -7
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/parser/arguments.rb +16 -16
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/parser/option.rb +42 -21
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/parser/options.rb +13 -10
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/rake_compat.rb +1 -1
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/runner.rb +35 -33
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/shell.rb +4 -4
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/shell/basic.rb +49 -33
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/shell/color.rb +2 -2
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/shell/html.rb +5 -5
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/util.rb +8 -7
- data/lib/bundler/vendor/{thor-0.19.1 → thor}/lib/thor/version.rb +1 -1
- data/lib/bundler/vendored_fileutils.rb +9 -0
- data/lib/bundler/vendored_molinillo.rb +4 -5
- data/lib/bundler/vendored_persistent.rb +45 -4
- data/lib/bundler/vendored_thor.rb +8 -5
- data/lib/bundler/version.rb +23 -1
- data/lib/bundler/version_ranges.rb +76 -0
- data/lib/bundler/vlad.rb +8 -2
- data/lib/bundler/worker.rb +39 -6
- data/lib/bundler/yaml_serializer.rb +90 -0
- data/man/bundle-add.1 +58 -0
- data/man/bundle-add.1.txt +52 -0
- data/man/bundle-add.ronn +40 -0
- data/man/bundle-binstubs.1 +40 -0
- data/man/bundle-binstubs.1.txt +48 -0
- data/man/bundle-binstubs.ronn +43 -0
- data/man/bundle-check.1 +31 -0
- data/man/bundle-check.1.txt +33 -0
- data/man/bundle-check.ronn +26 -0
- data/man/bundle-clean.1 +24 -0
- data/man/bundle-clean.1.txt +26 -0
- data/man/bundle-clean.ronn +18 -0
- data/man/bundle-config.1 +497 -0
- data/man/bundle-config.1.txt +529 -0
- data/man/bundle-config.ronn +256 -31
- data/man/bundle-doctor.1 +44 -0
- data/man/bundle-doctor.1.txt +44 -0
- data/man/bundle-doctor.ronn +33 -0
- data/man/bundle-exec.1 +165 -0
- data/man/bundle-exec.1.txt +178 -0
- data/man/bundle-exec.ronn +19 -3
- data/man/bundle-gem.1 +80 -0
- data/man/bundle-gem.1.txt +91 -0
- data/man/bundle-gem.ronn +78 -0
- data/man/bundle-info.1 +20 -0
- data/man/bundle-info.1.txt +21 -0
- data/man/bundle-info.ronn +17 -0
- data/man/bundle-init.1 +25 -0
- data/man/bundle-init.1.txt +34 -0
- data/man/bundle-init.ronn +29 -0
- data/man/bundle-inject.1 +33 -0
- data/man/bundle-inject.1.txt +32 -0
- data/man/bundle-inject.ronn +22 -0
- data/man/bundle-install.1 +308 -0
- data/man/bundle-install.1.txt +396 -0
- data/man/bundle-install.ronn +64 -67
- data/man/bundle-list.1 +50 -0
- data/man/bundle-list.1.txt +43 -0
- data/man/bundle-list.ronn +33 -0
- data/man/bundle-lock.1 +84 -0
- data/man/bundle-lock.1.txt +93 -0
- data/man/bundle-lock.ronn +94 -0
- data/man/bundle-open.1 +32 -0
- data/man/bundle-open.1.txt +29 -0
- data/man/bundle-open.ronn +19 -0
- data/man/bundle-outdated.1 +155 -0
- data/man/bundle-outdated.1.txt +131 -0
- data/man/bundle-outdated.ronn +111 -0
- data/man/bundle-package.1 +55 -0
- data/man/bundle-package.1.txt +79 -0
- data/man/bundle-package.ronn +14 -8
- data/man/bundle-platform.1 +61 -0
- data/man/bundle-platform.1.txt +57 -0
- data/man/bundle-platform.ronn +1 -1
- data/man/bundle-pristine.1 +34 -0
- data/man/bundle-pristine.1.txt +44 -0
- data/man/bundle-pristine.ronn +34 -0
- data/man/bundle-remove.1 +31 -0
- data/man/bundle-remove.1.txt +34 -0
- data/man/bundle-remove.ronn +23 -0
- data/man/bundle-show.1 +23 -0
- data/man/bundle-show.1.txt +27 -0
- data/man/bundle-show.ronn +21 -0
- data/man/bundle-update.1 +394 -0
- data/man/bundle-update.1.txt +391 -0
- data/man/bundle-update.ronn +180 -18
- data/man/bundle-viz.1 +39 -0
- data/man/bundle-viz.1.txt +39 -0
- data/man/bundle-viz.ronn +30 -0
- data/man/bundle.1 +136 -0
- data/man/bundle.1.txt +116 -0
- data/man/bundle.ronn +46 -33
- data/man/gemfile.5 +689 -0
- data/man/gemfile.5.ronn +127 -79
- data/man/gemfile.5.txt +653 -0
- data/man/index.txt +25 -7
- metadata +242 -95
- data/.gitignore +0 -16
- data/.rspec +0 -3
- data/.travis.yml +0 -110
- data/CODE_OF_CONDUCT.md +0 -40
- data/CONTRIBUTING.md +0 -32
- data/DEVELOPMENT.md +0 -119
- data/ISSUES.md +0 -96
- data/Rakefile +0 -302
- data/UPGRADING.md +0 -103
- data/bin/bundle +0 -21
- data/bin/bundler +0 -21
- data/lib/bundler/anonymizable_uri.rb +0 -32
- data/lib/bundler/environment.rb +0 -42
- data/lib/bundler/gem_installer.rb +0 -9
- data/lib/bundler/gem_path_manipulation.rb +0 -8
- data/lib/bundler/ssl_certs/AddTrustExternalCARoot.pem +0 -32
- data/lib/bundler/ssl_certs/Class3PublicPrimaryCertificationAuthority.pem +0 -14
- data/lib/bundler/ssl_certs/EntrustnetSecureServerCertificationAuthority.pem +0 -28
- data/lib/bundler/ssl_certs/GeoTrustGlobalCA.pem +0 -20
- data/lib/bundler/templates/newgem/.travis.yml.tt +0 -3
- data/lib/bundler/templates/newgem/test/minitest_helper.rb.tt +0 -4
- data/lib/bundler/vendor/Molinillo-0.2.1/lib/molinillo.rb +0 -5
- data/lib/bundler/vendor/Molinillo-0.2.1/lib/molinillo/dependency_graph.rb +0 -266
- data/lib/bundler/vendor/Molinillo-0.2.1/lib/molinillo/errors.rb +0 -69
- data/lib/bundler/vendor/Molinillo-0.2.1/lib/molinillo/gem_metadata.rb +0 -3
- data/lib/bundler/vendor/Molinillo-0.2.1/lib/molinillo/resolution.rb +0 -412
- data/lib/bundler/vendor/Molinillo-0.2.1/lib/molinillo/state.rb +0 -43
- data/lib/bundler/vendor/thor-0.19.1/lib/thor/core_ext/io_binary_read.rb +0 -10
- data/lib/bundler/vendor/thor-0.19.1/lib/thor/core_ext/ordered_hash.rb +0 -98
- data/lib/bundler/vendor/thor-0.19.1/lib/thor/parser.rb +0 -4
@@ -0,0 +1,396 @@
|
|
1
|
+
BUNDLE-INSTALL(1) BUNDLE-INSTALL(1)
|
2
|
+
|
3
|
+
|
4
|
+
|
5
|
+
NAME
|
6
|
+
bundle-install - Install the dependencies specified in your Gemfile
|
7
|
+
|
8
|
+
SYNOPSIS
|
9
|
+
bundle install [--binstubs[=DIRECTORY]] [--clean] [--deployment]
|
10
|
+
[--force] [--frozen] [--full-index] [--gemfile=GEMFILE] [--jobs=NUMBER]
|
11
|
+
[--local] [--no-cache] [--no-prune] [--path PATH] [--quiet]
|
12
|
+
[--retry=NUMBER] [--shebang] [--standalone[=GROUP[ GROUP...]]] [--sys-
|
13
|
+
tem] [--trust-policy=POLICY] [--with=GROUP[ GROUP...]] [--with-
|
14
|
+
out=GROUP[ GROUP...]]
|
15
|
+
|
16
|
+
DESCRIPTION
|
17
|
+
Install the gems specified in your Gemfile(5). If this is the first
|
18
|
+
time you run bundle install (and a Gemfile.lock does not exist),
|
19
|
+
Bundler will fetch all remote sources, resolve dependencies and install
|
20
|
+
all needed gems.
|
21
|
+
|
22
|
+
If a Gemfile.lock does exist, and you have not updated your Gemfile(5),
|
23
|
+
Bundler will fetch all remote sources, but use the dependencies speci-
|
24
|
+
fied in the Gemfile.lock instead of resolving dependencies.
|
25
|
+
|
26
|
+
If a Gemfile.lock does exist, and you have updated your Gemfile(5),
|
27
|
+
Bundler will use the dependencies in the Gemfile.lock for all gems that
|
28
|
+
you did not update, but will re-resolve the dependencies of gems that
|
29
|
+
you did update. You can find more information about this update process
|
30
|
+
below under CONSERVATIVE UPDATING.
|
31
|
+
|
32
|
+
OPTIONS
|
33
|
+
To apply any of --binstubs, --deployment, --path, or --without every
|
34
|
+
time bundle install is run, use bundle config (see bundle-config(1)).
|
35
|
+
|
36
|
+
--binstubs[=<directory>]
|
37
|
+
Creates a directory (defaults to ~/bin) and place any executa-
|
38
|
+
bles from the gem there. These executables run in Bundler's con-
|
39
|
+
text. If used, you might add this directory to your environ-
|
40
|
+
ment's PATH variable. For instance, if the rails gem comes with
|
41
|
+
a rails executable, this flag will create a bin/rails executable
|
42
|
+
that ensures that all referred dependencies will be resolved
|
43
|
+
using the bundled gems.
|
44
|
+
|
45
|
+
--clean
|
46
|
+
On finishing the installation Bundler is going to remove any
|
47
|
+
gems not present in the current Gemfile(5). Don't worry, gems
|
48
|
+
currently in use will not be removed.
|
49
|
+
|
50
|
+
--deployment
|
51
|
+
In deployment mode, Bundler will 'roll-out' the bundle for pro-
|
52
|
+
duction or CI use. Please check carefully if you want to have
|
53
|
+
this option enabled in your development environment.
|
54
|
+
|
55
|
+
--force
|
56
|
+
Force download every gem, even if the required versions are
|
57
|
+
already available locally. --redownload is an alias of this
|
58
|
+
option.
|
59
|
+
|
60
|
+
--frozen
|
61
|
+
Do not allow the Gemfile.lock to be updated after this install.
|
62
|
+
Exits non-zero if there are going to be changes to the Gem-
|
63
|
+
file.lock.
|
64
|
+
|
65
|
+
--full-index
|
66
|
+
Bundler will not call Rubygems' API endpoint (default) but down-
|
67
|
+
load and cache a (currently big) index file of all gems. Perfor-
|
68
|
+
mance can be improved for large bundles that seldom change by
|
69
|
+
enabling this option.
|
70
|
+
|
71
|
+
--gemfile=<gemfile>
|
72
|
+
The location of the Gemfile(5) which Bundler should use. This
|
73
|
+
defaults to a Gemfile(5) in the current working directory. In
|
74
|
+
general, Bundler will assume that the location of the Gemfile(5)
|
75
|
+
is also the project's root and will try to find Gemfile.lock and
|
76
|
+
vendor/cache relative to this location.
|
77
|
+
|
78
|
+
--jobs=[<number>], -j[<number>]
|
79
|
+
The maximum number of parallel download and install jobs. The
|
80
|
+
default is 1.
|
81
|
+
|
82
|
+
--local
|
83
|
+
Do not attempt to connect to rubygems.org. Instead, Bundler will
|
84
|
+
use the gems already present in Rubygems' cache or in ven-
|
85
|
+
dor/cache. Note that if a appropriate platform-specific gem
|
86
|
+
exists on rubygems.org it will not be found.
|
87
|
+
|
88
|
+
--no-cache
|
89
|
+
Do not update the cache in vendor/cache with the newly bundled
|
90
|
+
gems. This does not remove any gems in the cache but keeps the
|
91
|
+
newly bundled gems from being cached during the install.
|
92
|
+
|
93
|
+
--no-prune
|
94
|
+
Don't remove stale gems from the cache when the installation
|
95
|
+
finishes.
|
96
|
+
|
97
|
+
--path=<path>
|
98
|
+
The location to install the specified gems to. This defaults to
|
99
|
+
Rubygems' setting. Bundler shares this location with Rubygems,
|
100
|
+
gem install ... will have gem installed there, too. Therefore,
|
101
|
+
gems installed without a --path ... setting will show up by
|
102
|
+
calling gem list. Accordingly, gems installed to other locations
|
103
|
+
will not get listed.
|
104
|
+
|
105
|
+
--quiet
|
106
|
+
Do not print progress information to the standard output.
|
107
|
+
Instead, Bundler will exit using a status code ($?).
|
108
|
+
|
109
|
+
--retry=[<number>]
|
110
|
+
Retry failed network or git requests for number times.
|
111
|
+
|
112
|
+
--shebang=<ruby-executable>
|
113
|
+
Uses the specified ruby executable (usually ruby) to execute the
|
114
|
+
scripts created with --binstubs. In addition, if you use --bin-
|
115
|
+
stubs together with --shebang jruby these executables will be
|
116
|
+
changed to execute jruby instead.
|
117
|
+
|
118
|
+
--standalone[=<list>]
|
119
|
+
Makes a bundle that can work without depending on Rubygems or
|
120
|
+
Bundler at runtime. A space separated list of groups to install
|
121
|
+
has to be specified. Bundler creates a directory named bundle
|
122
|
+
and installs the bundle there. It also generates a bun-
|
123
|
+
dle/bundler/setup.rb file to replace Bundler's own setup in the
|
124
|
+
manner required. Using this option implicitly sets path, which
|
125
|
+
is a [remembered option][REMEMBERED OPTIONS].
|
126
|
+
|
127
|
+
--system
|
128
|
+
Installs the gems specified in the bundle to the system's
|
129
|
+
Rubygems location. This overrides any previous configuration of
|
130
|
+
--path.
|
131
|
+
|
132
|
+
--trust-policy=[<policy>]
|
133
|
+
Apply the Rubygems security policy policy, where policy is one
|
134
|
+
of HighSecurity, MediumSecurity, LowSecurity, AlmostNoSecurity,
|
135
|
+
or NoSecurity. For more details, please see the Rubygems signing
|
136
|
+
documentation linked below in SEE ALSO.
|
137
|
+
|
138
|
+
--with=<list>
|
139
|
+
A space-separated list of groups referencing gems to install. If
|
140
|
+
an optional group is given it is installed. If a group is given
|
141
|
+
that is in the remembered list of groups given to --without, it
|
142
|
+
is removed from that list.
|
143
|
+
|
144
|
+
--without=<list>
|
145
|
+
A space-separated list of groups referencing gems to skip during
|
146
|
+
installation. If a group is given that is in the remembered list
|
147
|
+
of groups given to --with, it is removed from that list.
|
148
|
+
|
149
|
+
DEPLOYMENT MODE
|
150
|
+
Bundler's defaults are optimized for development. To switch to defaults
|
151
|
+
optimized for deployment and for CI, use the --deployment flag. Do not
|
152
|
+
activate deployment mode on development machines, as it will cause an
|
153
|
+
error when the Gemfile(5) is modified.
|
154
|
+
|
155
|
+
1. A Gemfile.lock is required.
|
156
|
+
|
157
|
+
To ensure that the same versions of the gems you developed with and
|
158
|
+
tested with are also used in deployments, a Gemfile.lock is
|
159
|
+
required.
|
160
|
+
|
161
|
+
This is mainly to ensure that you remember to check your Gem-
|
162
|
+
file.lock into version control.
|
163
|
+
|
164
|
+
2. The Gemfile.lock must be up to date
|
165
|
+
|
166
|
+
In development, you can modify your Gemfile(5) and re-run bundle
|
167
|
+
install to conservatively update your Gemfile.lock snapshot.
|
168
|
+
|
169
|
+
In deployment, your Gemfile.lock should be up-to-date with changes
|
170
|
+
made in your Gemfile(5).
|
171
|
+
|
172
|
+
3. Gems are installed to vendor/bundle not your default system loca-
|
173
|
+
tion
|
174
|
+
|
175
|
+
In development, it's convenient to share the gems used in your
|
176
|
+
application with other applications and other scripts that run on
|
177
|
+
the system.
|
178
|
+
|
179
|
+
In deployment, isolation is a more important default. In addition,
|
180
|
+
the user deploying the application may not have permission to
|
181
|
+
install gems to the system, or the web server may not have permis-
|
182
|
+
sion to read them.
|
183
|
+
|
184
|
+
As a result, bundle install --deployment installs gems to the ven-
|
185
|
+
dor/bundle directory in the application. This may be overridden
|
186
|
+
using the --path option.
|
187
|
+
|
188
|
+
|
189
|
+
|
190
|
+
SUDO USAGE
|
191
|
+
By default, Bundler installs gems to the same location as gem install.
|
192
|
+
|
193
|
+
In some cases, that location may not be writable by your Unix user. In
|
194
|
+
that case, Bundler will stage everything in a temporary directory, then
|
195
|
+
ask you for your sudo password in order to copy the gems into their
|
196
|
+
system location.
|
197
|
+
|
198
|
+
From your perspective, this is identical to installing the gems
|
199
|
+
directly into the system.
|
200
|
+
|
201
|
+
You should never use sudo bundle install. This is because several other
|
202
|
+
steps in bundle install must be performed as the current user:
|
203
|
+
|
204
|
+
o Updating your Gemfile.lock
|
205
|
+
|
206
|
+
o Updating your vendor/cache, if necessary
|
207
|
+
|
208
|
+
o Checking out private git repositories using your user's SSH keys
|
209
|
+
|
210
|
+
|
211
|
+
|
212
|
+
Of these three, the first two could theoretically be performed by
|
213
|
+
chowning the resulting files to $SUDO_USER. The third, however, can
|
214
|
+
only be performed by invoking the git command as the current user.
|
215
|
+
Therefore, git gems are downloaded and installed into ~/.bundle rather
|
216
|
+
than $GEM_HOME or $BUNDLE_PATH.
|
217
|
+
|
218
|
+
As a result, you should run bundle install as the current user, and
|
219
|
+
Bundler will ask for your password if it is needed to put the gems into
|
220
|
+
their final location.
|
221
|
+
|
222
|
+
INSTALLING GROUPS
|
223
|
+
By default, bundle install will install all gems in all groups in your
|
224
|
+
Gemfile(5), except those declared for a different platform.
|
225
|
+
|
226
|
+
However, you can explicitly tell Bundler to skip installing certain
|
227
|
+
groups with the --without option. This option takes a space-separated
|
228
|
+
list of groups.
|
229
|
+
|
230
|
+
While the --without option will skip installing the gems in the speci-
|
231
|
+
fied groups, it will still download those gems and use them to resolve
|
232
|
+
the dependencies of every gem in your Gemfile(5).
|
233
|
+
|
234
|
+
This is so that installing a different set of groups on another machine
|
235
|
+
(such as a production server) will not change the gems and versions
|
236
|
+
that you have already developed and tested against.
|
237
|
+
|
238
|
+
Bundler offers a rock-solid guarantee that the third-party code you are
|
239
|
+
running in development and testing is also the third-party code you are
|
240
|
+
running in production. You can choose to exclude some of that code in
|
241
|
+
different environments, but you will never be caught flat-footed by
|
242
|
+
different versions of third-party code being used in different environ-
|
243
|
+
ments.
|
244
|
+
|
245
|
+
For a simple illustration, consider the following Gemfile(5):
|
246
|
+
|
247
|
+
|
248
|
+
|
249
|
+
source 'https://rubygems.org'
|
250
|
+
|
251
|
+
gem 'sinatra'
|
252
|
+
|
253
|
+
group :production do
|
254
|
+
gem 'rack-perftools-profiler'
|
255
|
+
end
|
256
|
+
|
257
|
+
|
258
|
+
|
259
|
+
In this case, sinatra depends on any version of Rack (>= 1.0), while
|
260
|
+
rack-perftools-profiler depends on 1.x (~> 1.0).
|
261
|
+
|
262
|
+
When you run bundle install --without production in development, we
|
263
|
+
look at the dependencies of rack-perftools-profiler as well. That way,
|
264
|
+
you do not spend all your time developing against Rack 2.0, using new
|
265
|
+
APIs unavailable in Rack 1.x, only to have Bundler switch to Rack 1.2
|
266
|
+
when the production group is used.
|
267
|
+
|
268
|
+
This should not cause any problems in practice, because we do not
|
269
|
+
attempt to install the gems in the excluded groups, and only evaluate
|
270
|
+
as part of the dependency resolution process.
|
271
|
+
|
272
|
+
This also means that you cannot include different versions of the same
|
273
|
+
gem in different groups, because doing so would result in different
|
274
|
+
sets of dependencies used in development and production. Because of the
|
275
|
+
vagaries of the dependency resolution process, this usually affects
|
276
|
+
more than the gems you list in your Gemfile(5), and can (surprisingly)
|
277
|
+
radically change the gems you are using.
|
278
|
+
|
279
|
+
THE GEMFILE.LOCK
|
280
|
+
When you run bundle install, Bundler will persist the full names and
|
281
|
+
versions of all gems that you used (including dependencies of the gems
|
282
|
+
specified in the Gemfile(5)) into a file called Gemfile.lock.
|
283
|
+
|
284
|
+
Bundler uses this file in all subsequent calls to bundle install, which
|
285
|
+
guarantees that you always use the same exact code, even as your appli-
|
286
|
+
cation moves across machines.
|
287
|
+
|
288
|
+
Because of the way dependency resolution works, even a seemingly small
|
289
|
+
change (for instance, an update to a point-release of a dependency of a
|
290
|
+
gem in your Gemfile(5)) can result in radically different gems being
|
291
|
+
needed to satisfy all dependencies.
|
292
|
+
|
293
|
+
As a result, you SHOULD check your Gemfile.lock into version control,
|
294
|
+
in both applications and gems. If you do not, every machine that checks
|
295
|
+
out your repository (including your production server) will resolve all
|
296
|
+
dependencies again, which will result in different versions of
|
297
|
+
third-party code being used if any of the gems in the Gemfile(5) or any
|
298
|
+
of their dependencies have been updated.
|
299
|
+
|
300
|
+
When Bundler first shipped, the Gemfile.lock was included in the .git-
|
301
|
+
ignore file included with generated gems. Over time, however, it became
|
302
|
+
clear that this practice forces the pain of broken dependencies onto
|
303
|
+
new contributors, while leaving existing contributors potentially
|
304
|
+
unaware of the problem. Since bundle install is usually the first step
|
305
|
+
towards a contribution, the pain of broken dependencies would discour-
|
306
|
+
age new contributors from contributing. As a result, we have revised
|
307
|
+
our guidance for gem authors to now recommend checking in the lock for
|
308
|
+
gems.
|
309
|
+
|
310
|
+
CONSERVATIVE UPDATING
|
311
|
+
When you make a change to the Gemfile(5) and then run bundle install,
|
312
|
+
Bundler will update only the gems that you modified.
|
313
|
+
|
314
|
+
In other words, if a gem that you did not modify worked before you
|
315
|
+
called bundle install, it will continue to use the exact same versions
|
316
|
+
of all dependencies as it used before the update.
|
317
|
+
|
318
|
+
Let's take a look at an example. Here's your original Gemfile(5):
|
319
|
+
|
320
|
+
|
321
|
+
|
322
|
+
source 'https://rubygems.org'
|
323
|
+
|
324
|
+
gem 'actionpack', '2.3.8'
|
325
|
+
gem 'activemerchant'
|
326
|
+
|
327
|
+
|
328
|
+
|
329
|
+
In this case, both actionpack and activemerchant depend on activesup-
|
330
|
+
port. The actionpack gem depends on activesupport 2.3.8 and rack ~>
|
331
|
+
1.1.0, while the activemerchant gem depends on activesupport >= 2.3.2,
|
332
|
+
braintree >= 2.0.0, and builder >= 2.0.0.
|
333
|
+
|
334
|
+
When the dependencies are first resolved, Bundler will select
|
335
|
+
activesupport 2.3.8, which satisfies the requirements of both gems in
|
336
|
+
your Gemfile(5).
|
337
|
+
|
338
|
+
Next, you modify your Gemfile(5) to:
|
339
|
+
|
340
|
+
|
341
|
+
|
342
|
+
source 'https://rubygems.org'
|
343
|
+
|
344
|
+
gem 'actionpack', '3.0.0.rc'
|
345
|
+
gem 'activemerchant'
|
346
|
+
|
347
|
+
|
348
|
+
|
349
|
+
The actionpack 3.0.0.rc gem has a number of new dependencies, and
|
350
|
+
updates the activesupport dependency to = 3.0.0.rc and the rack depen-
|
351
|
+
dency to ~> 1.2.1.
|
352
|
+
|
353
|
+
When you run bundle install, Bundler notices that you changed the
|
354
|
+
actionpack gem, but not the activemerchant gem. It evaluates the gems
|
355
|
+
currently being used to satisfy its requirements:
|
356
|
+
|
357
|
+
activesupport 2.3.8
|
358
|
+
also used to satisfy a dependency in activemerchant, which is
|
359
|
+
not being updated
|
360
|
+
|
361
|
+
rack ~> 1.1.0
|
362
|
+
not currently being used to satisfy another dependency
|
363
|
+
|
364
|
+
Because you did not explicitly ask to update activemerchant, you would
|
365
|
+
not expect it to suddenly stop working after updating actionpack. How-
|
366
|
+
ever, satisfying the new activesupport 3.0.0.rc dependency of action-
|
367
|
+
pack requires updating one of its dependencies.
|
368
|
+
|
369
|
+
Even though activemerchant declares a very loose dependency that theo-
|
370
|
+
retically matches activesupport 3.0.0.rc, Bundler treats gems in your
|
371
|
+
Gemfile(5) that have not changed as an atomic unit together with their
|
372
|
+
dependencies. In this case, the activemerchant dependency is treated as
|
373
|
+
activemerchant 1.7.1 + activesupport 2.3.8, so bundle install will
|
374
|
+
report that it cannot update actionpack.
|
375
|
+
|
376
|
+
To explicitly update actionpack, including its dependencies which other
|
377
|
+
gems in the Gemfile(5) still depend on, run bundle update actionpack
|
378
|
+
(see bundle update(1)).
|
379
|
+
|
380
|
+
Summary: In general, after making a change to the Gemfile(5) , you
|
381
|
+
should first try to run bundle install, which will guarantee that no
|
382
|
+
other gem in the Gemfile(5) is impacted by the change. If that does not
|
383
|
+
work, run bundle update(1) bundle-update.1.html.
|
384
|
+
|
385
|
+
SEE ALSO
|
386
|
+
o Gem install docs
|
387
|
+
http://guides.rubygems.org/rubygems-basics/#installing-gems
|
388
|
+
|
389
|
+
o Rubygems signing docs http://guides.rubygems.org/security/
|
390
|
+
|
391
|
+
|
392
|
+
|
393
|
+
|
394
|
+
|
395
|
+
|
396
|
+
December 2018 BUNDLE-INSTALL(1)
|
data/man/bundle-install.ronn
CHANGED
@@ -5,18 +5,23 @@ bundle-install(1) -- Install the dependencies specified in your Gemfile
|
|
5
5
|
|
6
6
|
`bundle install` [--binstubs[=DIRECTORY]]
|
7
7
|
[--clean]
|
8
|
+
[--deployment]
|
9
|
+
[--force]
|
10
|
+
[--frozen]
|
8
11
|
[--full-index]
|
9
12
|
[--gemfile=GEMFILE]
|
10
13
|
[--jobs=NUMBER]
|
11
|
-
[--local]
|
14
|
+
[--local]
|
12
15
|
[--no-cache]
|
13
16
|
[--no-prune]
|
14
|
-
[--path PATH]
|
17
|
+
[--path PATH]
|
15
18
|
[--quiet]
|
16
19
|
[--retry=NUMBER]
|
17
20
|
[--shebang]
|
18
21
|
[--standalone[=GROUP[ GROUP...]]]
|
22
|
+
[--system]
|
19
23
|
[--trust-policy=POLICY]
|
24
|
+
[--with=GROUP[ GROUP...]]
|
20
25
|
[--without=GROUP[ GROUP...]]
|
21
26
|
|
22
27
|
## DESCRIPTION
|
@@ -38,6 +43,9 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
38
43
|
|
39
44
|
## OPTIONS
|
40
45
|
|
46
|
+
To apply any of `--binstubs`, `--deployment`, `--path`, or `--without` every
|
47
|
+
time `bundle install` is run, use `bundle config` (see bundle-config(1)).
|
48
|
+
|
41
49
|
* `--binstubs[=<directory>]`:
|
42
50
|
Creates a directory (defaults to `~/bin`) and place any executables from the
|
43
51
|
gem there. These executables run in Bundler's context. If used, you might add
|
@@ -51,10 +59,23 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
51
59
|
in the current Gemfile(5). Don't worry, gems currently in use will not be
|
52
60
|
removed.
|
53
61
|
|
62
|
+
* `--deployment`:
|
63
|
+
In [deployment mode][DEPLOYMENT MODE], Bundler will 'roll-out' the bundle for
|
64
|
+
production or CI use. Please check carefully if you want to have this option
|
65
|
+
enabled in your development environment.
|
66
|
+
|
67
|
+
* `--force`:
|
68
|
+
Force download every gem, even if the required versions are already available
|
69
|
+
locally. `--redownload` is an alias of this option.
|
70
|
+
|
71
|
+
* `--frozen`:
|
72
|
+
Do not allow the Gemfile.lock to be updated after this install. Exits
|
73
|
+
non-zero if there are going to be changes to the Gemfile.lock.
|
74
|
+
|
54
75
|
* `--full-index`:
|
55
76
|
Bundler will not call Rubygems' API endpoint (default) but download and cache
|
56
77
|
a (currently big) index file of all gems. Performance can be improved for
|
57
|
-
large bundles that
|
78
|
+
large bundles that seldom change by enabling this option.
|
58
79
|
|
59
80
|
* `--gemfile=<gemfile>`:
|
60
81
|
The location of the Gemfile(5) which Bundler should use. This defaults
|
@@ -63,8 +84,9 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
63
84
|
root and will try to find `Gemfile.lock` and `vendor/cache` relative
|
64
85
|
to this location.
|
65
86
|
|
66
|
-
* `--jobs=[<number>]`:
|
67
|
-
|
87
|
+
* `--jobs=[<number>]`, `-j[<number>]`:
|
88
|
+
The maximum number of parallel download and install jobs. The default
|
89
|
+
is `1`.
|
68
90
|
|
69
91
|
* `--local`:
|
70
92
|
Do not attempt to connect to `rubygems.org`. Instead, Bundler will use the
|
@@ -72,15 +94,6 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
72
94
|
appropriate platform-specific gem exists on `rubygems.org` it will not be
|
73
95
|
found.
|
74
96
|
|
75
|
-
* `--deployment`:
|
76
|
-
In [deployment mode][DEPLOYMENT MODE], Bundler will 'roll-out' the bundle for
|
77
|
-
`production` use. Please check carefully if you want to have this option
|
78
|
-
enabled in `development` or `test` environments.
|
79
|
-
|
80
|
-
* `--system`:
|
81
|
-
Installs the gems specified in the bundle to the system's Rubygems location.
|
82
|
-
This overrides any previous [remembered][REMEMBERED OPTIONS] use of `--path`.
|
83
|
-
|
84
97
|
* `--no-cache`:
|
85
98
|
Do not update the cache in `vendor/cache` with the newly bundled gems. This
|
86
99
|
does not remove any gems in the cache but keeps the newly bundled gems from
|
@@ -93,9 +106,8 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
93
106
|
The location to install the specified gems to. This defaults to Rubygems'
|
94
107
|
setting. Bundler shares this location with Rubygems, `gem install ...` will
|
95
108
|
have gem installed there, too. Therefore, gems installed without a
|
96
|
-
`--path ...` setting will show up by calling `gem list`.
|
97
|
-
installed to other locations will not get listed.
|
98
|
-
[remembered option][REMEMBERED OPTIONS].
|
109
|
+
`--path ...` setting will show up by calling `gem list`. Accordingly, gems
|
110
|
+
installed to other locations will not get listed.
|
99
111
|
|
100
112
|
* `--quiet`:
|
101
113
|
Do not print progress information to the standard output. Instead, Bundler
|
@@ -115,7 +127,12 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
115
127
|
runtime. A space separated list of groups to install has to be specified.
|
116
128
|
Bundler creates a directory named `bundle` and installs the bundle there. It
|
117
129
|
also generates a `bundle/bundler/setup.rb` file to replace Bundler's own setup
|
118
|
-
in the manner required.
|
130
|
+
in the manner required. Using this option implicitly sets `path`, which is a
|
131
|
+
[remembered option][REMEMBERED OPTIONS].
|
132
|
+
|
133
|
+
* `--system`:
|
134
|
+
Installs the gems specified in the bundle to the system's Rubygems location.
|
135
|
+
This overrides any previous configuration of `--path`.
|
119
136
|
|
120
137
|
* `--trust-policy=[<policy>]`:
|
121
138
|
Apply the Rubygems security policy <policy>, where policy is one of
|
@@ -123,16 +140,22 @@ update process below under [CONSERVATIVE UPDATING][].
|
|
123
140
|
`NoSecurity`. For more details, please see the Rubygems signing documentation
|
124
141
|
linked below in [SEE ALSO][].
|
125
142
|
|
143
|
+
* `--with=<list>`:
|
144
|
+
A space-separated list of groups referencing gems to install. If an
|
145
|
+
optional group is given it is installed. If a group is given that is
|
146
|
+
in the remembered list of groups given to --without, it is removed
|
147
|
+
from that list.
|
148
|
+
|
126
149
|
* `--without=<list>`:
|
127
150
|
A space-separated list of groups referencing gems to skip during installation.
|
128
|
-
|
129
|
-
|
151
|
+
If a group is given that is in the remembered list of groups given
|
152
|
+
to --with, it is removed from that list.
|
130
153
|
|
131
154
|
## DEPLOYMENT MODE
|
132
155
|
|
133
156
|
Bundler's defaults are optimized for development. To switch to
|
134
|
-
defaults optimized for deployment, use the `--deployment`
|
135
|
-
Do not activate deployment mode on development machines, as it
|
157
|
+
defaults optimized for deployment and for CI, use the `--deployment`
|
158
|
+
flag. Do not activate deployment mode on development machines, as it
|
136
159
|
will cause an error when the Gemfile(5) is modified.
|
137
160
|
|
138
161
|
1. A `Gemfile.lock` is required.
|
@@ -156,7 +179,7 @@ will cause an error when the Gemfile(5) is modified.
|
|
156
179
|
3. Gems are installed to `vendor/bundle` not your default system location
|
157
180
|
|
158
181
|
In development, it's convenient to share the gems used in your
|
159
|
-
application with other applications and other scripts run on
|
182
|
+
application with other applications and other scripts that run on
|
160
183
|
the system.
|
161
184
|
|
162
185
|
In deployment, isolation is a more important default. In addition,
|
@@ -177,7 +200,7 @@ that case, Bundler will stage everything in a temporary directory,
|
|
177
200
|
then ask you for your `sudo` password in order to copy the gems into
|
178
201
|
their system location.
|
179
202
|
|
180
|
-
From your perspective, this is identical to installing
|
203
|
+
From your perspective, this is identical to installing the gems
|
181
204
|
directly into the system.
|
182
205
|
|
183
206
|
You should never use `sudo bundle install`. This is because several
|
@@ -189,7 +212,7 @@ other steps in `bundle install` must be performed as the current user:
|
|
189
212
|
|
190
213
|
Of these three, the first two could theoretically be performed by
|
191
214
|
`chown`ing the resulting files to `$SUDO_USER`. The third, however,
|
192
|
-
can only be performed by
|
215
|
+
can only be performed by invoking the `git` command as
|
193
216
|
the current user. Therefore, git gems are downloaded and installed
|
194
217
|
into `~/.bundle` rather than $GEM_HOME or $BUNDLE_PATH.
|
195
218
|
|
@@ -248,44 +271,9 @@ This also means that you cannot include different versions of the same
|
|
248
271
|
gem in different groups, because doing so would result in different
|
249
272
|
sets of dependencies used in development and production. Because of
|
250
273
|
the vagaries of the dependency resolution process, this usually
|
251
|
-
affects more than
|
274
|
+
affects more than the gems you list in your Gemfile(5), and can
|
252
275
|
(surprisingly) radically change the gems you are using.
|
253
276
|
|
254
|
-
## REMEMBERED OPTIONS
|
255
|
-
|
256
|
-
Some options (marked above in the [OPTIONS][] section) are remembered
|
257
|
-
between calls to `bundle install`, and by the Bundler runtime.
|
258
|
-
|
259
|
-
For instance, if you run `bundle install --without test`, a subsequent
|
260
|
-
call to `bundle install` that does not include a `--without` flag will
|
261
|
-
remember your previous choice.
|
262
|
-
|
263
|
-
In addition, a call to `Bundler.setup` will not attempt to make the
|
264
|
-
gems in those groups available on the Ruby load path, as they were
|
265
|
-
not installed.
|
266
|
-
|
267
|
-
The settings that are remembered are:
|
268
|
-
|
269
|
-
* `--deployment`:
|
270
|
-
At runtime, this remembered setting will also result in Bundler
|
271
|
-
raising an exception if the `Gemfile.lock` is out of date.
|
272
|
-
|
273
|
-
* `--path`:
|
274
|
-
Subsequent calls to `bundle install` will install gems to the
|
275
|
-
directory originally passed to `--path`. The Bundler runtime
|
276
|
-
will look for gems in that location. You can revert this
|
277
|
-
option by running `bundle install --system`.
|
278
|
-
|
279
|
-
* `--binstubs`:
|
280
|
-
Bundler will update the executables every subsequent call to
|
281
|
-
`bundle install`.
|
282
|
-
|
283
|
-
* `--without`:
|
284
|
-
As described above, Bundler will skip the gems specified by
|
285
|
-
`--without` in subsequent calls to `bundle install`. The
|
286
|
-
Bundler runtime will also not try to make the gems in the
|
287
|
-
skipped groups available.
|
288
|
-
|
289
277
|
## THE GEMFILE.LOCK
|
290
278
|
|
291
279
|
When you run `bundle install`, Bundler will persist the full names
|
@@ -302,12 +290,21 @@ of a dependency of a gem in your Gemfile(5)) can result in radically
|
|
302
290
|
different gems being needed to satisfy all dependencies.
|
303
291
|
|
304
292
|
As a result, you `SHOULD` check your `Gemfile.lock` into version
|
305
|
-
control. If you do not, every machine that
|
306
|
-
repository (including your production server) will resolve all
|
293
|
+
control, in both applications and gems. If you do not, every machine that
|
294
|
+
checks out your repository (including your production server) will resolve all
|
307
295
|
dependencies again, which will result in different versions of
|
308
296
|
third-party code being used if `any` of the gems in the Gemfile(5)
|
309
297
|
or any of their dependencies have been updated.
|
310
298
|
|
299
|
+
When Bundler first shipped, the `Gemfile.lock` was included in the `.gitignore`
|
300
|
+
file included with generated gems. Over time, however, it became clear that
|
301
|
+
this practice forces the pain of broken dependencies onto new contributors,
|
302
|
+
while leaving existing contributors potentially unaware of the problem. Since
|
303
|
+
`bundle install` is usually the first step towards a contribution, the pain of
|
304
|
+
broken dependencies would discourage new contributors from contributing. As a
|
305
|
+
result, we have revised our guidance for gem authors to now recommend checking
|
306
|
+
in the lock for gems.
|
307
|
+
|
311
308
|
## CONSERVATIVE UPDATING
|
312
309
|
|
313
310
|
When you make a change to the Gemfile(5) and then run `bundle install`,
|
@@ -372,10 +369,10 @@ which other gems in the Gemfile(5) still depend on, run
|
|
372
369
|
|
373
370
|
`Summary`: In general, after making a change to the Gemfile(5) , you
|
374
371
|
should first try to run `bundle install`, which will guarantee that no
|
375
|
-
other
|
376
|
-
does not work, run [bundle update(1)]
|
372
|
+
other gem in the Gemfile(5) is impacted by the change. If that
|
373
|
+
does not work, run [bundle update(1)](bundle-update.1.html).
|
377
374
|
|
378
375
|
## SEE ALSO
|
379
376
|
|
380
|
-
* Gem install docs
|
381
|
-
* Rubygems signing docs
|
377
|
+
* [Gem install docs](http://guides.rubygems.org/rubygems-basics/#installing-gems)
|
378
|
+
* [Rubygems signing docs](http://guides.rubygems.org/security/)
|