bundler 1.17.2 → 2.2.33
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +2095 -1251
- data/LICENSE.md +18 -19
- data/README.md +10 -11
- data/bundler.gemspec +10 -28
- data/exe/bundle +22 -3
- data/lib/bundler/build_metadata.rb +4 -12
- data/lib/bundler/capistrano.rb +4 -4
- data/lib/bundler/cli/add.rb +28 -16
- data/lib/bundler/cli/binstubs.rb +6 -2
- data/lib/bundler/cli/cache.rb +24 -17
- data/lib/bundler/cli/check.rb +4 -2
- data/lib/bundler/cli/clean.rb +1 -1
- data/lib/bundler/cli/common.rb +39 -13
- data/lib/bundler/cli/config.rb +161 -86
- data/lib/bundler/cli/console.rb +1 -1
- data/lib/bundler/cli/doctor.rb +20 -9
- data/lib/bundler/cli/exec.rb +8 -25
- data/lib/bundler/cli/fund.rb +36 -0
- data/lib/bundler/cli/gem.rb +213 -32
- data/lib/bundler/cli/info.rb +42 -7
- data/lib/bundler/cli/init.rb +2 -2
- data/lib/bundler/cli/inject.rb +1 -1
- data/lib/bundler/cli/install.rb +34 -44
- data/lib/bundler/cli/issue.rb +8 -7
- data/lib/bundler/cli/list.rb +19 -11
- data/lib/bundler/cli/lock.rb +5 -1
- data/lib/bundler/cli/open.rb +11 -8
- data/lib/bundler/cli/outdated.rb +142 -118
- data/lib/bundler/cli/plugin.rb +19 -2
- data/lib/bundler/cli/pristine.rb +6 -1
- data/lib/bundler/cli/remove.rb +1 -2
- data/lib/bundler/cli/show.rb +2 -2
- data/lib/bundler/cli/update.rb +43 -16
- data/lib/bundler/cli.rb +211 -150
- data/lib/bundler/compact_index_client/cache.rb +6 -14
- data/lib/bundler/compact_index_client/gem_parser.rb +28 -0
- data/lib/bundler/compact_index_client/updater.rb +15 -28
- data/lib/bundler/compact_index_client.rb +28 -12
- data/lib/bundler/current_ruby.rb +14 -11
- data/lib/bundler/definition.rb +207 -368
- data/lib/bundler/dep_proxy.rb +16 -9
- data/lib/bundler/dependency.rb +19 -14
- data/lib/bundler/deployment.rb +1 -1
- data/lib/bundler/digest.rb +71 -0
- data/lib/bundler/dsl.rb +81 -81
- data/lib/bundler/endpoint_specification.rb +1 -1
- data/lib/bundler/env.rb +9 -14
- data/lib/bundler/environment_preserver.rb +29 -3
- data/lib/bundler/errors.rb +20 -3
- data/lib/bundler/feature_flag.rb +14 -33
- data/lib/bundler/fetcher/base.rb +1 -1
- data/lib/bundler/fetcher/compact_index.rb +28 -14
- data/lib/bundler/fetcher/dependency.rb +1 -1
- data/lib/bundler/fetcher/downloader.rb +14 -8
- data/lib/bundler/fetcher/index.rb +8 -8
- data/lib/bundler/fetcher.rb +22 -17
- data/lib/bundler/friendly_errors.rb +29 -48
- data/lib/bundler/gem_helper.rb +79 -43
- data/lib/bundler/gem_helpers.rb +38 -29
- data/lib/bundler/gem_tasks.rb +1 -1
- data/lib/bundler/gem_version_promoter.rb +5 -5
- data/lib/bundler/graph.rb +3 -3
- data/lib/bundler/index.rb +9 -9
- data/lib/bundler/injector.rb +33 -13
- data/lib/bundler/inline.rb +41 -30
- data/lib/bundler/installer/gem_installer.rb +9 -18
- data/lib/bundler/installer/parallel_installer.rb +50 -33
- data/lib/bundler/installer/standalone.rb +30 -11
- data/lib/bundler/installer.rb +39 -66
- data/lib/bundler/lazy_specification.rb +63 -28
- data/lib/bundler/lockfile_generator.rb +1 -1
- data/lib/bundler/lockfile_parser.rb +19 -52
- data/lib/bundler/{ssl_certs → man}/.document +0 -0
- data/{man → lib/bundler/man}/bundle-add.1 +10 -2
- data/{man/bundle-add.ronn → lib/bundler/man/bundle-add.1.ronn} +7 -1
- data/{man → lib/bundler/man}/bundle-binstubs.1 +6 -4
- data/{man/bundle-binstubs.ronn → lib/bundler/man/bundle-binstubs.1.ronn} +3 -5
- data/lib/bundler/man/bundle-cache.1 +55 -0
- data/{man/bundle-package.ronn → lib/bundler/man/bundle-cache.1.ronn} +15 -15
- data/{man → lib/bundler/man}/bundle-check.1 +1 -1
- data/{man/bundle-check.ronn → lib/bundler/man/bundle-check.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-clean.1 +1 -1
- data/{man/bundle-clean.ronn → lib/bundler/man/bundle-clean.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-config.1 +59 -60
- data/{man/bundle-config.ronn → lib/bundler/man/bundle-config.1.ronn} +77 -78
- data/{man → lib/bundler/man}/bundle-doctor.1 +1 -1
- data/{man/bundle-doctor.ronn → lib/bundler/man/bundle-doctor.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-exec.1 +2 -2
- data/{man/bundle-exec.ronn → lib/bundler/man/bundle-exec.1.ronn} +1 -1
- data/{man → lib/bundler/man}/bundle-gem.1 +38 -3
- data/{man/bundle-gem.ronn → lib/bundler/man/bundle-gem.1.ronn} +46 -7
- data/{man → lib/bundler/man}/bundle-info.1 +1 -1
- data/{man/bundle-info.ronn → lib/bundler/man/bundle-info.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-init.1 +2 -2
- data/{man/bundle-init.ronn → lib/bundler/man/bundle-init.1.ronn} +1 -1
- data/{man → lib/bundler/man}/bundle-inject.1 +1 -1
- data/{man/bundle-inject.ronn → lib/bundler/man/bundle-inject.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-install.1 +37 -7
- data/{man/bundle-install.ronn → lib/bundler/man/bundle-install.1.ronn} +34 -7
- data/{man → lib/bundler/man}/bundle-list.1 +7 -7
- data/{man/bundle-list.ronn → lib/bundler/man/bundle-list.1.ronn} +6 -6
- data/{man → lib/bundler/man}/bundle-lock.1 +1 -1
- data/{man/bundle-lock.ronn → lib/bundler/man/bundle-lock.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-open.1 +1 -1
- data/{man/bundle-open.ronn → lib/bundler/man/bundle-open.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-outdated.1 +1 -1
- data/{man/bundle-outdated.ronn → lib/bundler/man/bundle-outdated.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-platform.1 +1 -1
- data/{man/bundle-platform.ronn → lib/bundler/man/bundle-platform.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-pristine.1 +1 -1
- data/{man/bundle-pristine.ronn → lib/bundler/man/bundle-pristine.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-remove.1 +1 -1
- data/{man/bundle-remove.ronn → lib/bundler/man/bundle-remove.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-show.1 +1 -1
- data/{man/bundle-show.ronn → lib/bundler/man/bundle-show.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle-update.1 +7 -7
- data/{man/bundle-update.ronn → lib/bundler/man/bundle-update.1.ronn} +6 -6
- data/{man → lib/bundler/man}/bundle-viz.1 +1 -1
- data/{man/bundle-viz.ronn → lib/bundler/man/bundle-viz.1.ronn} +0 -0
- data/{man → lib/bundler/man}/bundle.1 +7 -3
- data/{man/bundle.ronn → lib/bundler/man/bundle.1.ronn} +5 -2
- data/{man → lib/bundler/man}/gemfile.5 +44 -21
- data/{man → lib/bundler/man}/gemfile.5.ronn +24 -20
- data/{man → lib/bundler/man}/index.txt +1 -1
- data/lib/bundler/match_platform.rb +1 -1
- data/lib/bundler/mirror.rb +5 -5
- data/lib/bundler/plugin/api/source.rb +27 -7
- data/lib/bundler/plugin/api.rb +1 -1
- data/lib/bundler/plugin/dsl.rb +1 -1
- data/lib/bundler/plugin/index.rb +27 -4
- data/lib/bundler/plugin/installer/rubygems.rb +1 -1
- data/lib/bundler/plugin/installer.rb +35 -22
- data/lib/bundler/plugin/source_list.rb +5 -1
- data/lib/bundler/plugin.rb +100 -42
- data/lib/bundler/psyched_yaml.rb +0 -15
- data/lib/bundler/remote_specification.rb +5 -4
- data/lib/bundler/resolver/spec_group.rb +57 -53
- data/lib/bundler/resolver.rb +127 -113
- data/lib/bundler/retry.rb +4 -4
- data/lib/bundler/ruby_version.rb +5 -20
- data/lib/bundler/rubygems_ext.rb +103 -79
- data/lib/bundler/rubygems_gem_installer.rb +69 -8
- data/lib/bundler/rubygems_integration.rb +181 -446
- data/lib/bundler/runtime.rb +24 -34
- data/lib/bundler/settings.rb +159 -110
- data/lib/bundler/setup.rb +11 -12
- data/lib/bundler/shared_helpers.rb +56 -90
- data/lib/bundler/similarity_detector.rb +3 -3
- data/lib/bundler/source/git/git_proxy.rb +106 -105
- data/lib/bundler/source/git.rb +66 -39
- data/lib/bundler/source/metadata.rb +9 -9
- data/lib/bundler/source/path/installer.rb +10 -10
- data/lib/bundler/source/path.rb +23 -12
- data/lib/bundler/source/rubygems/remote.rb +3 -4
- data/lib/bundler/source/rubygems.rb +136 -120
- data/lib/bundler/source/rubygems_aggregate.rb +68 -0
- data/lib/bundler/source.rb +27 -6
- data/lib/bundler/source_list.rb +101 -66
- data/lib/bundler/source_map.rb +58 -0
- data/lib/bundler/spec_set.rb +49 -53
- data/lib/bundler/stub_specification.rb +40 -34
- data/lib/bundler/templates/Executable.bundler +24 -15
- data/lib/bundler/templates/Gemfile +1 -1
- data/lib/bundler/templates/gems.rb +1 -1
- data/lib/bundler/templates/newgem/CHANGELOG.md.tt +5 -0
- data/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt +57 -47
- data/lib/bundler/templates/newgem/Gemfile.tt +19 -2
- data/lib/bundler/templates/newgem/README.md.tt +7 -5
- data/lib/bundler/templates/newgem/Rakefile.tt +23 -5
- data/lib/bundler/templates/newgem/bin/console.tt +1 -0
- data/lib/bundler/templates/newgem/circleci/config.yml.tt +13 -0
- data/lib/bundler/templates/newgem/ext/newgem/extconf.rb.tt +2 -0
- data/lib/bundler/templates/newgem/github/workflows/main.yml.tt +27 -0
- data/lib/bundler/templates/newgem/gitlab-ci.yml.tt +9 -0
- data/lib/bundler/templates/newgem/lib/newgem/version.rb.tt +2 -0
- data/lib/bundler/templates/newgem/lib/newgem.rb.tt +4 -2
- data/lib/bundler/templates/newgem/newgem.gemspec.tt +29 -40
- data/lib/bundler/templates/newgem/rubocop.yml.tt +13 -0
- data/lib/bundler/templates/newgem/sig/newgem.rbs.tt +8 -0
- data/lib/bundler/templates/newgem/spec/newgem_spec.rb.tt +2 -0
- data/lib/bundler/templates/newgem/spec/spec_helper.rb.tt +2 -1
- data/lib/bundler/templates/newgem/standard.yml.tt +2 -0
- data/lib/bundler/templates/newgem/test/{newgem_test.rb.tt → minitest/newgem_test.rb.tt} +2 -0
- data/lib/bundler/templates/newgem/test/minitest/test_helper.rb.tt +6 -0
- data/lib/bundler/templates/newgem/test/test-unit/newgem_test.rb.tt +15 -0
- data/lib/bundler/templates/newgem/test/test-unit/test_helper.rb.tt +6 -0
- data/lib/bundler/templates/newgem/travis.yml.tt +0 -1
- data/lib/bundler/ui/rg_proxy.rb +1 -1
- data/lib/bundler/ui/shell.rb +7 -11
- data/lib/bundler/ui.rb +3 -3
- data/lib/bundler/uri_credentials_filter.rb +10 -4
- data/lib/bundler/vendor/.document +1 -0
- data/lib/bundler/vendor/connection_pool/LICENSE +20 -0
- data/lib/bundler/vendor/connection_pool/lib/connection_pool/timed_stack.rb +174 -0
- data/lib/bundler/vendor/connection_pool/lib/connection_pool/version.rb +3 -0
- data/lib/bundler/vendor/connection_pool/lib/connection_pool/wrapper.rb +57 -0
- data/lib/bundler/vendor/connection_pool/lib/connection_pool.rb +126 -0
- data/lib/bundler/vendor/fileutils/LICENSE.txt +22 -0
- data/lib/bundler/vendor/fileutils/lib/fileutils.rb +273 -147
- data/lib/bundler/vendor/molinillo/LICENSE +9 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/specification_provider.rb +7 -0
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_edge_no_circular.rb +1 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_vertex.rb +1 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/delete_edge.rb +1 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/detach_vertex_named.rb +1 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/log.rb +6 -6
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/set_payload.rb +1 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/tag.rb +3 -3
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/vertex.rb +39 -11
- data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph.rb +38 -6
- data/lib/bundler/vendor/molinillo/lib/molinillo/errors.rb +4 -4
- data/lib/bundler/vendor/molinillo/lib/molinillo/gem_metadata.rb +1 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/modules/specification_provider.rb +12 -1
- data/lib/bundler/vendor/molinillo/lib/molinillo/resolution.rb +53 -51
- data/lib/bundler/vendor/molinillo/lib/molinillo/resolver.rb +2 -2
- data/lib/bundler/vendor/molinillo/lib/molinillo.rb +5 -6
- data/lib/bundler/vendor/net-http-persistent/README.rdoc +82 -0
- data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent/connection.rb +40 -0
- data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent/pool.rb +53 -0
- data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent/timed_stack_multi.rb +79 -0
- data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent.rb +302 -462
- data/lib/bundler/vendor/thor/LICENSE.md +20 -0
- data/lib/bundler/vendor/thor/lib/thor/actions/create_file.rb +1 -1
- data/lib/bundler/vendor/thor/lib/thor/actions/create_link.rb +3 -2
- data/lib/bundler/vendor/thor/lib/thor/actions/directory.rb +7 -17
- data/lib/bundler/vendor/thor/lib/thor/actions/file_manipulation.rb +20 -9
- data/lib/bundler/vendor/thor/lib/thor/actions/inject_into_file.rb +19 -8
- data/lib/bundler/vendor/thor/lib/thor/actions.rb +28 -13
- data/lib/bundler/vendor/thor/lib/thor/base.rb +63 -43
- data/lib/bundler/vendor/thor/lib/thor/command.rb +21 -14
- data/lib/bundler/vendor/thor/lib/thor/error.rb +78 -0
- data/lib/bundler/vendor/thor/lib/thor/group.rb +3 -3
- data/lib/bundler/vendor/thor/lib/thor/invocation.rb +1 -0
- data/lib/bundler/vendor/thor/lib/thor/line_editor/basic.rb +1 -1
- data/lib/bundler/vendor/thor/lib/thor/line_editor/readline.rb +6 -6
- data/lib/bundler/vendor/thor/lib/thor/line_editor.rb +2 -2
- data/lib/bundler/vendor/thor/lib/thor/nested_context.rb +29 -0
- data/lib/bundler/vendor/thor/lib/thor/parser/arguments.rb +7 -3
- data/lib/bundler/vendor/thor/lib/thor/parser/option.rb +20 -7
- data/lib/bundler/vendor/thor/lib/thor/parser/options.rb +21 -5
- data/lib/bundler/vendor/thor/lib/thor/parser.rb +4 -4
- data/lib/bundler/vendor/thor/lib/thor/rake_compat.rb +1 -0
- data/lib/bundler/vendor/thor/lib/thor/runner.rb +15 -14
- data/lib/bundler/vendor/thor/lib/thor/shell/basic.rb +65 -8
- data/lib/bundler/vendor/thor/lib/thor/shell/color.rb +10 -2
- data/lib/bundler/vendor/thor/lib/thor/shell/html.rb +3 -3
- data/lib/bundler/vendor/thor/lib/thor/shell.rb +4 -4
- data/lib/bundler/vendor/thor/lib/thor/util.rb +18 -2
- data/lib/bundler/vendor/thor/lib/thor/version.rb +1 -1
- data/lib/bundler/vendor/thor/lib/thor.rb +16 -9
- data/lib/bundler/vendor/tmpdir/lib/tmpdir.rb +154 -0
- data/lib/bundler/vendor/tsort/LICENSE.txt +22 -0
- data/lib/bundler/vendor/tsort/lib/tsort.rb +453 -0
- data/lib/bundler/vendor/uri/LICENSE.txt +22 -0
- data/lib/bundler/vendor/uri/lib/uri/common.rb +744 -0
- data/lib/bundler/vendor/uri/lib/uri/file.rb +94 -0
- data/lib/bundler/vendor/uri/lib/uri/ftp.rb +267 -0
- data/lib/bundler/vendor/uri/lib/uri/generic.rb +1568 -0
- data/lib/bundler/vendor/uri/lib/uri/http.rb +88 -0
- data/lib/bundler/vendor/uri/lib/uri/https.rb +23 -0
- data/lib/bundler/vendor/uri/lib/uri/ldap.rb +261 -0
- data/lib/bundler/vendor/uri/lib/uri/ldaps.rb +21 -0
- data/lib/bundler/vendor/uri/lib/uri/mailto.rb +294 -0
- data/lib/bundler/vendor/uri/lib/uri/rfc2396_parser.rb +546 -0
- data/lib/bundler/vendor/uri/lib/uri/rfc3986_parser.rb +125 -0
- data/lib/bundler/vendor/uri/lib/uri/version.rb +6 -0
- data/lib/bundler/vendor/uri/lib/uri.rb +104 -0
- data/lib/bundler/vendored_fileutils.rb +1 -6
- data/lib/bundler/vendored_molinillo.rb +1 -1
- data/lib/bundler/vendored_persistent.rb +7 -12
- data/lib/bundler/vendored_thor.rb +2 -2
- data/lib/bundler/vendored_tmpdir.rb +4 -0
- data/lib/bundler/vendored_tsort.rb +4 -0
- data/lib/bundler/vendored_uri.rb +4 -0
- data/lib/bundler/version.rb +1 -20
- data/lib/bundler/version_ranges.rb +51 -5
- data/lib/bundler/vlad.rb +2 -2
- data/lib/bundler/worker.rb +21 -8
- data/lib/bundler/yaml_serializer.rb +3 -4
- data/lib/bundler.rb +248 -118
- metadata +115 -190
- data/exe/bundle_ruby +0 -60
- data/lib/bundler/cli/package.rb +0 -49
- data/lib/bundler/compatibility_guard.rb +0 -14
- data/lib/bundler/gem_remote_fetcher.rb +0 -43
- data/lib/bundler/ssl_certs/certificate_manager.rb +0 -66
- data/lib/bundler/ssl_certs/index.rubygems.org/GlobalSignRootCA.pem +0 -21
- data/lib/bundler/ssl_certs/rubygems.global.ssl.fastly.net/DigiCertHighAssuranceEVRootCA.pem +0 -23
- data/lib/bundler/ssl_certs/rubygems.org/AddTrustExternalCARoot.pem +0 -25
- data/lib/bundler/templates/newgem/test/test_helper.rb.tt +0 -4
- data/lib/bundler/vendor/molinillo/lib/molinillo/compatibility.rb +0 -26
- data/lib/bundler/vendor/net-http-persistent/lib/net/http/faster.rb +0 -27
- data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent/ssl_reuse.rb +0 -129
- data/lib/bundler/vendor/thor/lib/thor/core_ext/io_binary_read.rb +0 -12
- data/lib/bundler/vendor/thor/lib/thor/core_ext/ordered_hash.rb +0 -129
- data/man/bundle-add.1.txt +0 -52
- data/man/bundle-binstubs.1.txt +0 -48
- data/man/bundle-check.1.txt +0 -33
- data/man/bundle-clean.1.txt +0 -26
- data/man/bundle-config.1.txt +0 -529
- data/man/bundle-doctor.1.txt +0 -44
- data/man/bundle-exec.1.txt +0 -178
- data/man/bundle-gem.1.txt +0 -91
- data/man/bundle-info.1.txt +0 -21
- data/man/bundle-init.1.txt +0 -34
- data/man/bundle-inject.1.txt +0 -32
- data/man/bundle-install.1.txt +0 -396
- data/man/bundle-list.1.txt +0 -43
- data/man/bundle-lock.1.txt +0 -93
- data/man/bundle-open.1.txt +0 -29
- data/man/bundle-outdated.1.txt +0 -131
- data/man/bundle-package.1 +0 -55
- data/man/bundle-package.1.txt +0 -79
- data/man/bundle-platform.1.txt +0 -57
- data/man/bundle-pristine.1.txt +0 -44
- data/man/bundle-remove.1.txt +0 -34
- data/man/bundle-show.1.txt +0 -27
- data/man/bundle-update.1.txt +0 -391
- data/man/bundle-viz.1.txt +0 -39
- data/man/bundle.1.txt +0 -113
- data/man/gemfile.5.txt +0 -653
data/man/bundle-package.1
DELETED
@@ -1,55 +0,0 @@
|
|
1
|
-
.\" generated with Ronn/v0.7.3
|
2
|
-
.\" http://github.com/rtomayko/ronn/tree/0.7.3
|
3
|
-
.
|
4
|
-
.TH "BUNDLE\-PACKAGE" "1" "November 2018" "" ""
|
5
|
-
.
|
6
|
-
.SH "NAME"
|
7
|
-
\fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
|
8
|
-
.
|
9
|
-
.SH "SYNOPSIS"
|
10
|
-
\fBbundle package\fR
|
11
|
-
.
|
12
|
-
.SH "DESCRIPTION"
|
13
|
-
Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
|
14
|
-
.
|
15
|
-
.SH "GIT AND PATH GEMS"
|
16
|
-
Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
|
17
|
-
.
|
18
|
-
.SH "SUPPORT FOR MULTIPLE PLATFORMS"
|
19
|
-
When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
|
20
|
-
.
|
21
|
-
.SH "REMOTE FETCHING"
|
22
|
-
By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
|
23
|
-
.
|
24
|
-
.P
|
25
|
-
For instance, consider this Gemfile(5):
|
26
|
-
.
|
27
|
-
.IP "" 4
|
28
|
-
.
|
29
|
-
.nf
|
30
|
-
|
31
|
-
source "https://rubygems\.org"
|
32
|
-
|
33
|
-
gem "nokogiri"
|
34
|
-
.
|
35
|
-
.fi
|
36
|
-
.
|
37
|
-
.IP "" 0
|
38
|
-
.
|
39
|
-
.P
|
40
|
-
If you run \fBbundle package\fR under C Ruby, bundler will retrieve the version of \fBnokogiri\fR for the \fB"ruby"\fR platform\. If you deploy to JRuby and run \fBbundle install\fR, bundler is forced to check to see whether a \fB"java"\fR platformed \fBnokogiri\fR exists\.
|
41
|
-
.
|
42
|
-
.P
|
43
|
-
Even though the \fBnokogiri\fR gem for the Ruby platform is \fItechnically\fR acceptable on JRuby, it has a C extension that does not run on JRuby\. As a result, bundler will, by default, still connect to \fBrubygems\.org\fR to check whether it has a version of one of your gems more specific to your platform\.
|
44
|
-
.
|
45
|
-
.P
|
46
|
-
This problem is also not limited to the \fB"java"\fR platform\. A similar (common) problem can happen when developing on Windows and deploying to Linux, or even when developing on OSX and deploying to Linux\.
|
47
|
-
.
|
48
|
-
.P
|
49
|
-
If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriate for the platform you are on, you can run \fBbundle install \-\-local\fR to skip checking for more appropriate gems, and use the ones in \fBvendor/cache\fR\.
|
50
|
-
.
|
51
|
-
.P
|
52
|
-
One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
|
53
|
-
.
|
54
|
-
.P
|
55
|
-
By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.
|
data/man/bundle-package.1.txt
DELETED
@@ -1,79 +0,0 @@
|
|
1
|
-
BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
NAME
|
6
|
-
bundle-package - Package your needed .gem files into your application
|
7
|
-
|
8
|
-
SYNOPSIS
|
9
|
-
bundle package
|
10
|
-
|
11
|
-
DESCRIPTION
|
12
|
-
Copy all of the .gem files needed to run the application into the ven-
|
13
|
-
dor/cache directory. In the future, when running [bundle
|
14
|
-
install(1)][bundle-install], use the gems in the cache in preference to
|
15
|
-
the ones on rubygems.org.
|
16
|
-
|
17
|
-
GIT AND PATH GEMS
|
18
|
-
Since Bundler 1.2, the bundle package command can also package :git and
|
19
|
-
:path dependencies besides .gem files. This needs to be explicitly
|
20
|
-
enabled via the --all option. Once used, the --all option will be
|
21
|
-
remembered.
|
22
|
-
|
23
|
-
SUPPORT FOR MULTIPLE PLATFORMS
|
24
|
-
When using gems that have different packages for different platforms,
|
25
|
-
Bundler 1.8 and newer support caching of gems for other platforms where
|
26
|
-
the Gemfile has been resolved (i.e. present in the lockfile) in ven-
|
27
|
-
dor/cache. This needs to be enabled via the --all-platforms option.
|
28
|
-
This setting will be remembered in your local bundler configuration.
|
29
|
-
|
30
|
-
REMOTE FETCHING
|
31
|
-
By default, if you run bundle install(1)](bundle-install.1.html) after
|
32
|
-
running bundle package(1) bundle-package.1.html, bundler will still
|
33
|
-
connect to rubygems.org to check whether a platform-specific gem exists
|
34
|
-
for any of the gems in vendor/cache.
|
35
|
-
|
36
|
-
For instance, consider this Gemfile(5):
|
37
|
-
|
38
|
-
|
39
|
-
|
40
|
-
source "https://rubygems.org"
|
41
|
-
|
42
|
-
gem "nokogiri"
|
43
|
-
|
44
|
-
|
45
|
-
|
46
|
-
If you run bundle package under C Ruby, bundler will retrieve the ver-
|
47
|
-
sion of nokogiri for the "ruby" platform. If you deploy to JRuby and
|
48
|
-
run bundle install, bundler is forced to check to see whether a "java"
|
49
|
-
platformed nokogiri exists.
|
50
|
-
|
51
|
-
Even though the nokogiri gem for the Ruby platform is technically
|
52
|
-
acceptable on JRuby, it has a C extension that does not run on JRuby.
|
53
|
-
As a result, bundler will, by default, still connect to rubygems.org to
|
54
|
-
check whether it has a version of one of your gems more specific to
|
55
|
-
your platform.
|
56
|
-
|
57
|
-
This problem is also not limited to the "java" platform. A similar
|
58
|
-
(common) problem can happen when developing on Windows and deploying to
|
59
|
-
Linux, or even when developing on OSX and deploying to Linux.
|
60
|
-
|
61
|
-
If you know for sure that the gems packaged in vendor/cache are appro-
|
62
|
-
priate for the platform you are on, you can run bundle install --local
|
63
|
-
to skip checking for more appropriate gems, and use the ones in ven-
|
64
|
-
dor/cache.
|
65
|
-
|
66
|
-
One way to be sure that you have the right platformed versions of all
|
67
|
-
your gems is to run bundle package on an identical machine and check in
|
68
|
-
the gems. For instance, you can run bundle package on an identical
|
69
|
-
staging box during your staging process, and check in the vendor/cache
|
70
|
-
before deploying to production.
|
71
|
-
|
72
|
-
By default, bundle package(1) bundle-package.1.html fetches and also
|
73
|
-
installs the gems to the default location. To package the dependencies
|
74
|
-
to vendor/cache without installing them to the local install location,
|
75
|
-
you can run bundle package --no-install.
|
76
|
-
|
77
|
-
|
78
|
-
|
79
|
-
November 2018 BUNDLE-PACKAGE(1)
|
data/man/bundle-platform.1.txt
DELETED
@@ -1,57 +0,0 @@
|
|
1
|
-
BUNDLE-PLATFORM(1) BUNDLE-PLATFORM(1)
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
NAME
|
6
|
-
bundle-platform - Displays platform compatibility information
|
7
|
-
|
8
|
-
SYNOPSIS
|
9
|
-
bundle platform [--ruby]
|
10
|
-
|
11
|
-
DESCRIPTION
|
12
|
-
platform will display information from your Gemfile, Gemfile.lock, and
|
13
|
-
Ruby VM about your platform.
|
14
|
-
|
15
|
-
For instance, using this Gemfile(5):
|
16
|
-
|
17
|
-
|
18
|
-
|
19
|
-
source "https://rubygems.org"
|
20
|
-
|
21
|
-
ruby "1.9.3"
|
22
|
-
|
23
|
-
gem "rack"
|
24
|
-
|
25
|
-
|
26
|
-
|
27
|
-
If you run bundle platform on Ruby 1.9.3, it will display the following
|
28
|
-
output:
|
29
|
-
|
30
|
-
|
31
|
-
|
32
|
-
Your platform is: x86_64-linux
|
33
|
-
|
34
|
-
Your app has gems that work on these platforms:
|
35
|
-
* ruby
|
36
|
-
|
37
|
-
Your Gemfile specifies a Ruby version requirement:
|
38
|
-
* ruby 1.9.3
|
39
|
-
|
40
|
-
Your current platform satisfies the Ruby version requirement.
|
41
|
-
|
42
|
-
|
43
|
-
|
44
|
-
platform will list all the platforms in your Gemfile.lock as well as
|
45
|
-
the ruby directive if applicable from your Gemfile(5). It will also let
|
46
|
-
you know if the ruby directive requirement has been met. If ruby direc-
|
47
|
-
tive doesn't match the running Ruby VM, it will tell you what part does
|
48
|
-
not.
|
49
|
-
|
50
|
-
OPTIONS
|
51
|
-
--ruby It will display the ruby directive information, so you don't
|
52
|
-
have to parse it from the Gemfile(5).
|
53
|
-
|
54
|
-
|
55
|
-
|
56
|
-
|
57
|
-
November 2018 BUNDLE-PLATFORM(1)
|
data/man/bundle-pristine.1.txt
DELETED
@@ -1,44 +0,0 @@
|
|
1
|
-
BUNDLE-PRISTINE(1) BUNDLE-PRISTINE(1)
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
NAME
|
6
|
-
bundle-pristine - Restores installed gems to their pristine condition
|
7
|
-
|
8
|
-
SYNOPSIS
|
9
|
-
bundle pristine
|
10
|
-
|
11
|
-
DESCRIPTION
|
12
|
-
pristine restores the installed gems in the bundle to their pristine
|
13
|
-
condition using the local gem cache from RubyGems. For git gems, a
|
14
|
-
forced checkout will be performed.
|
15
|
-
|
16
|
-
For further explanation, bundle pristine ignores unpacked files on
|
17
|
-
disk. In other words, this command utilizes the local .gem cache or the
|
18
|
-
gem's git repository as if one were installing from scratch.
|
19
|
-
|
20
|
-
Note: the Bundler gem cannot be restored to its original state with
|
21
|
-
pristine. One also cannot use bundle pristine on gems with a 'path'
|
22
|
-
option in the Gemfile, because bundler has no original copy it can
|
23
|
-
restore from.
|
24
|
-
|
25
|
-
When is it practical to use bundle pristine?
|
26
|
-
|
27
|
-
It comes in handy when a developer is debugging a gem. bundle pristine
|
28
|
-
is a great way to get rid of experimental changes to a gem that one may
|
29
|
-
not want.
|
30
|
-
|
31
|
-
Why use bundle pristine over gem pristine --all?
|
32
|
-
|
33
|
-
Both commands are very similar. For context: bundle pristine, without
|
34
|
-
arguments, cleans all gems from the lockfile. Meanwhile, gem pristine
|
35
|
-
--all cleans all installed gems for that Ruby version.
|
36
|
-
|
37
|
-
If a developer forgets which gems in their project they might have been
|
38
|
-
debugging, the Rubygems gem pristine [GEMNAME] command may be inconve-
|
39
|
-
nient. One can avoid waiting for gem pristine --all, and instead run
|
40
|
-
bundle pristine.
|
41
|
-
|
42
|
-
|
43
|
-
|
44
|
-
November 2018 BUNDLE-PRISTINE(1)
|
data/man/bundle-remove.1.txt
DELETED
@@ -1,34 +0,0 @@
|
|
1
|
-
BUNDLE-REMOVE(1) BUNDLE-REMOVE(1)
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
NAME
|
6
|
-
bundle-remove - Removes gems from the Gemfile
|
7
|
-
|
8
|
-
SYNOPSIS
|
9
|
-
bundle remove [GEM [GEM ...]] [--install]
|
10
|
-
|
11
|
-
DESCRIPTION
|
12
|
-
Removes the given gems from the Gemfile while ensuring that the result-
|
13
|
-
ing Gemfile is still valid. If a gem cannot be removed, a warning is
|
14
|
-
printed. If a gem is already absent from the Gemfile, and error is
|
15
|
-
raised.
|
16
|
-
|
17
|
-
OPTIONS
|
18
|
-
--install
|
19
|
-
Runs bundle install after the given gems have been removed from
|
20
|
-
the Gemfile, which ensures that both the lockfile and the
|
21
|
-
installed gems on disk are also updated to remove the given
|
22
|
-
gem(s).
|
23
|
-
|
24
|
-
Example:
|
25
|
-
|
26
|
-
bundle remove rails
|
27
|
-
|
28
|
-
bundle remove rails rack
|
29
|
-
|
30
|
-
bundle remove rails rack --install
|
31
|
-
|
32
|
-
|
33
|
-
|
34
|
-
November 2018 BUNDLE-REMOVE(1)
|
data/man/bundle-show.1.txt
DELETED
@@ -1,27 +0,0 @@
|
|
1
|
-
BUNDLE-SHOW(1) BUNDLE-SHOW(1)
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
NAME
|
6
|
-
bundle-show - Shows all the gems in your bundle, or the path to a gem
|
7
|
-
|
8
|
-
SYNOPSIS
|
9
|
-
bundle show [GEM] [--paths]
|
10
|
-
|
11
|
-
DESCRIPTION
|
12
|
-
Without the [GEM] option, show will print a list of the names and ver-
|
13
|
-
sions of all gems that are required by your [Gemfile(5)][Gemfile(5)],
|
14
|
-
sorted by name.
|
15
|
-
|
16
|
-
Calling show with [GEM] will list the exact location of that gem on
|
17
|
-
your machine.
|
18
|
-
|
19
|
-
OPTIONS
|
20
|
-
--paths
|
21
|
-
List the paths of all gems that are required by your [Gem-
|
22
|
-
file(5)][Gemfile(5)], sorted by gem name.
|
23
|
-
|
24
|
-
|
25
|
-
|
26
|
-
|
27
|
-
November 2018 BUNDLE-SHOW(1)
|
data/man/bundle-update.1.txt
DELETED
@@ -1,391 +0,0 @@
|
|
1
|
-
BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
NAME
|
6
|
-
bundle-update - Update your gems to the latest available versions
|
7
|
-
|
8
|
-
SYNOPSIS
|
9
|
-
bundle update *gems [--all] [--group=NAME] [--source=NAME] [--local]
|
10
|
-
[--ruby] [--bundler[=VERSION]] [--full-index] [--jobs=JOBS] [--quiet]
|
11
|
-
[--force] [--patch|--minor|--major] [--strict] [--conservative]
|
12
|
-
|
13
|
-
DESCRIPTION
|
14
|
-
Update the gems specified (all gems, if --all flag is used), ignoring
|
15
|
-
the previously installed gems specified in the Gemfile.lock. In gen-
|
16
|
-
eral, you should use bundle install(1) bundle-install.1.html to install
|
17
|
-
the same exact gems and versions across machines.
|
18
|
-
|
19
|
-
You would use bundle update to explicitly update the version of a gem.
|
20
|
-
|
21
|
-
OPTIONS
|
22
|
-
--all Update all gems specified in Gemfile.
|
23
|
-
|
24
|
-
--group=<name>, -g=[<name>]
|
25
|
-
Only update the gems in the specified group. For instance, you
|
26
|
-
can update all gems in the development group with bundle update
|
27
|
-
--group development. You can also call bundle update rails
|
28
|
-
--group test to update the rails gem and all gems in the test
|
29
|
-
group, for example.
|
30
|
-
|
31
|
-
--source=<name>
|
32
|
-
The name of a :git or :path source used in the Gemfile(5). For
|
33
|
-
instance, with a :git source of
|
34
|
-
http://github.com/rails/rails.git, you would call bundle update
|
35
|
-
--source rails
|
36
|
-
|
37
|
-
--local
|
38
|
-
Do not attempt to fetch gems remotely and use the gem cache
|
39
|
-
instead.
|
40
|
-
|
41
|
-
--ruby Update the locked version of Ruby to the current version of
|
42
|
-
Ruby.
|
43
|
-
|
44
|
-
--bundler
|
45
|
-
Update the locked version of bundler to the invoked bundler ver-
|
46
|
-
sion.
|
47
|
-
|
48
|
-
--full-index
|
49
|
-
Fall back to using the single-file index of all gems.
|
50
|
-
|
51
|
-
--jobs=[<number>], -j[<number>]
|
52
|
-
Specify the number of jobs to run in parallel. The default is 1.
|
53
|
-
|
54
|
-
--retry=[<number>]
|
55
|
-
Retry failed network or git requests for number times.
|
56
|
-
|
57
|
-
--quiet
|
58
|
-
Only output warnings and errors.
|
59
|
-
|
60
|
-
--force
|
61
|
-
Force downloading every gem. --redownload is an alias of this
|
62
|
-
option.
|
63
|
-
|
64
|
-
--patch
|
65
|
-
Prefer updating only to next patch version.
|
66
|
-
|
67
|
-
--minor
|
68
|
-
Prefer updating only to next minor version.
|
69
|
-
|
70
|
-
--major
|
71
|
-
Prefer updating to next major version (default).
|
72
|
-
|
73
|
-
--strict
|
74
|
-
Do not allow any gem to be updated past latest --patch | --minor
|
75
|
-
| --major.
|
76
|
-
|
77
|
-
--conservative
|
78
|
-
Use bundle install conservative update behavior and do not allow
|
79
|
-
shared dependencies to be updated.
|
80
|
-
|
81
|
-
UPDATING ALL GEMS
|
82
|
-
If you run bundle update --all, bundler will ignore any previously
|
83
|
-
installed gems and resolve all dependencies again based on the latest
|
84
|
-
versions of all gems available in the sources.
|
85
|
-
|
86
|
-
Consider the following Gemfile(5):
|
87
|
-
|
88
|
-
|
89
|
-
|
90
|
-
source "https://rubygems.org"
|
91
|
-
|
92
|
-
gem "rails", "3.0.0.rc"
|
93
|
-
gem "nokogiri"
|
94
|
-
|
95
|
-
|
96
|
-
|
97
|
-
When you run bundle install(1) bundle-install.1.html the first time,
|
98
|
-
bundler will resolve all of the dependencies, all the way down, and
|
99
|
-
install what you need:
|
100
|
-
|
101
|
-
|
102
|
-
|
103
|
-
Fetching gem metadata from https://rubygems.org/.........
|
104
|
-
Resolving dependencies...
|
105
|
-
Installing builder 2.1.2
|
106
|
-
Installing abstract 1.0.0
|
107
|
-
Installing rack 1.2.8
|
108
|
-
Using bundler 1.7.6
|
109
|
-
Installing rake 10.4.0
|
110
|
-
Installing polyglot 0.3.5
|
111
|
-
Installing mime-types 1.25.1
|
112
|
-
Installing i18n 0.4.2
|
113
|
-
Installing mini_portile 0.6.1
|
114
|
-
Installing tzinfo 0.3.42
|
115
|
-
Installing rack-mount 0.6.14
|
116
|
-
Installing rack-test 0.5.7
|
117
|
-
Installing treetop 1.4.15
|
118
|
-
Installing thor 0.14.6
|
119
|
-
Installing activesupport 3.0.0.rc
|
120
|
-
Installing erubis 2.6.6
|
121
|
-
Installing activemodel 3.0.0.rc
|
122
|
-
Installing arel 0.4.0
|
123
|
-
Installing mail 2.2.20
|
124
|
-
Installing activeresource 3.0.0.rc
|
125
|
-
Installing actionpack 3.0.0.rc
|
126
|
-
Installing activerecord 3.0.0.rc
|
127
|
-
Installing actionmailer 3.0.0.rc
|
128
|
-
Installing railties 3.0.0.rc
|
129
|
-
Installing rails 3.0.0.rc
|
130
|
-
Installing nokogiri 1.6.5
|
131
|
-
|
132
|
-
Bundle complete! 2 Gemfile dependencies, 26 gems total.
|
133
|
-
Use `bundle show [gemname]` to see where a bundled gem is installed.
|
134
|
-
|
135
|
-
|
136
|
-
|
137
|
-
As you can see, even though you have two gems in the Gemfile(5), your
|
138
|
-
application needs 26 different gems in order to run. Bundler remembers
|
139
|
-
the exact versions it installed in Gemfile.lock. The next time you run
|
140
|
-
bundle install(1) bundle-install.1.html, bundler skips the dependency
|
141
|
-
resolution and installs the same gems as it installed last time.
|
142
|
-
|
143
|
-
After checking in the Gemfile.lock into version control and cloning it
|
144
|
-
on another machine, running bundle install(1) bundle-install.1.html
|
145
|
-
will still install the gems that you installed last time. You don't
|
146
|
-
need to worry that a new release of erubis or mail changes the gems you
|
147
|
-
use.
|
148
|
-
|
149
|
-
However, from time to time, you might want to update the gems you are
|
150
|
-
using to the newest versions that still match the gems in your Gem-
|
151
|
-
file(5).
|
152
|
-
|
153
|
-
To do this, run bundle update --all, which will ignore the Gem-
|
154
|
-
file.lock, and resolve all the dependencies again. Keep in mind that
|
155
|
-
this process can result in a significantly different set of the 25
|
156
|
-
gems, based on the requirements of new gems that the gem authors
|
157
|
-
released since the last time you ran bundle update --all.
|
158
|
-
|
159
|
-
UPDATING A LIST OF GEMS
|
160
|
-
Sometimes, you want to update a single gem in the Gemfile(5), and leave
|
161
|
-
the rest of the gems that you specified locked to the versions in the
|
162
|
-
Gemfile.lock.
|
163
|
-
|
164
|
-
For instance, in the scenario above, imagine that nokogiri releases
|
165
|
-
version 1.4.4, and you want to update it without updating Rails and all
|
166
|
-
of its dependencies. To do this, run bundle update nokogiri.
|
167
|
-
|
168
|
-
Bundler will update nokogiri and any of its dependencies, but leave
|
169
|
-
alone Rails and its dependencies.
|
170
|
-
|
171
|
-
OVERLAPPING DEPENDENCIES
|
172
|
-
Sometimes, multiple gems declared in your Gemfile(5) are satisfied by
|
173
|
-
the same second-level dependency. For instance, consider the case of
|
174
|
-
thin and rack-perftools-profiler.
|
175
|
-
|
176
|
-
|
177
|
-
|
178
|
-
source "https://rubygems.org"
|
179
|
-
|
180
|
-
gem "thin"
|
181
|
-
gem "rack-perftools-profiler"
|
182
|
-
|
183
|
-
|
184
|
-
|
185
|
-
The thin gem depends on rack >= 1.0, while rack-perftools-profiler
|
186
|
-
depends on rack ~> 1.0. If you run bundle install, you get:
|
187
|
-
|
188
|
-
|
189
|
-
|
190
|
-
Fetching source index for https://rubygems.org/
|
191
|
-
Installing daemons (1.1.0)
|
192
|
-
Installing eventmachine (0.12.10) with native extensions
|
193
|
-
Installing open4 (1.0.1)
|
194
|
-
Installing perftools.rb (0.4.7) with native extensions
|
195
|
-
Installing rack (1.2.1)
|
196
|
-
Installing rack-perftools_profiler (0.0.2)
|
197
|
-
Installing thin (1.2.7) with native extensions
|
198
|
-
Using bundler (1.0.0.rc.3)
|
199
|
-
|
200
|
-
|
201
|
-
|
202
|
-
In this case, the two gems have their own set of dependencies, but they
|
203
|
-
share rack in common. If you run bundle update thin, bundler will
|
204
|
-
update daemons, eventmachine and rack, which are dependencies of thin,
|
205
|
-
but not open4 or perftools.rb, which are dependencies of
|
206
|
-
rack-perftools_profiler. Note that bundle update thin will update rack
|
207
|
-
even though it's also a dependency of rack-perftools_profiler.
|
208
|
-
|
209
|
-
In short, by default, when you update a gem using bundle update,
|
210
|
-
bundler will update all dependencies of that gem, including those that
|
211
|
-
are also dependencies of another gem.
|
212
|
-
|
213
|
-
To prevent updating shared dependencies, prior to version 1.14 the only
|
214
|
-
option was the CONSERVATIVE UPDATING behavior in bundle install(1) bun-
|
215
|
-
dle-install.1.html:
|
216
|
-
|
217
|
-
In this scenario, updating the thin version manually in the Gemfile(5),
|
218
|
-
and then running bundle install(1) bundle-install.1.html will only
|
219
|
-
update daemons and eventmachine, but not rack. For more information,
|
220
|
-
see the CONSERVATIVE UPDATING section of bundle install(1) bun-
|
221
|
-
dle-install.1.html.
|
222
|
-
|
223
|
-
Starting with 1.14, specifying the --conservative option will also pre-
|
224
|
-
vent shared dependencies from being updated.
|
225
|
-
|
226
|
-
PATCH LEVEL OPTIONS
|
227
|
-
Version 1.14 introduced 4 patch-level options that will influence how
|
228
|
-
gem versions are resolved. One of the following options can be used:
|
229
|
-
--patch, --minor or --major. --strict can be added to further influence
|
230
|
-
resolution.
|
231
|
-
|
232
|
-
--patch
|
233
|
-
Prefer updating only to next patch version.
|
234
|
-
|
235
|
-
--minor
|
236
|
-
Prefer updating only to next minor version.
|
237
|
-
|
238
|
-
--major
|
239
|
-
Prefer updating to next major version (default).
|
240
|
-
|
241
|
-
--strict
|
242
|
-
Do not allow any gem to be updated past latest --patch | --minor
|
243
|
-
| --major.
|
244
|
-
|
245
|
-
When Bundler is resolving what versions to use to satisfy declared
|
246
|
-
requirements in the Gemfile or in parent gems, it looks up all avail-
|
247
|
-
able versions, filters out any versions that don't satisfy the require-
|
248
|
-
ment, and then, by default, sorts them from newest to oldest, consider-
|
249
|
-
ing them in that order.
|
250
|
-
|
251
|
-
Providing one of the patch level options (e.g. --patch) changes the
|
252
|
-
sort order of the satisfying versions, causing Bundler to consider the
|
253
|
-
latest --patch or --minor version available before other versions. Note
|
254
|
-
that versions outside the stated patch level could still be resolved to
|
255
|
-
if necessary to find a suitable dependency graph.
|
256
|
-
|
257
|
-
For example, if gem 'foo' is locked at 1.0.2, with no gem requirement
|
258
|
-
defined in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0
|
259
|
-
all exist, the default order of preference by default (--major) will be
|
260
|
-
"2.0.0, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2".
|
261
|
-
|
262
|
-
If the --patch option is used, the order of preference will change to
|
263
|
-
"1.0.4, 1.0.3, 1.0.2, 1.1.1, 1.1.0, 2.0.0".
|
264
|
-
|
265
|
-
If the --minor option is used, the order of preference will change to
|
266
|
-
"1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0".
|
267
|
-
|
268
|
-
Combining the --strict option with any of the patch level options will
|
269
|
-
remove any versions beyond the scope of the patch level option, to
|
270
|
-
ensure that no gem is updated that far.
|
271
|
-
|
272
|
-
To continue the previous example, if both --patch and --strict options
|
273
|
-
are used, the available versions for resolution would be "1.0.4, 1.0.3,
|
274
|
-
1.0.2". If --minor and --strict are used, it would be "1.1.1, 1.1.0,
|
275
|
-
1.0.4, 1.0.3, 1.0.2".
|
276
|
-
|
277
|
-
Gem requirements as defined in the Gemfile will still be the first
|
278
|
-
determining factor for what versions are available. If the gem require-
|
279
|
-
ment for foo in the Gemfile is '~> 1.0', that will accomplish the same
|
280
|
-
thing as providing the --minor and --strict options.
|
281
|
-
|
282
|
-
PATCH LEVEL EXAMPLES
|
283
|
-
Given the following gem specifications:
|
284
|
-
|
285
|
-
|
286
|
-
|
287
|
-
foo 1.4.3, requires: ~> bar 2.0
|
288
|
-
foo 1.4.4, requires: ~> bar 2.0
|
289
|
-
foo 1.4.5, requires: ~> bar 2.1
|
290
|
-
foo 1.5.0, requires: ~> bar 2.1
|
291
|
-
foo 1.5.1, requires: ~> bar 3.0
|
292
|
-
bar with versions 2.0.3, 2.0.4, 2.1.0, 2.1.1, 3.0.0
|
293
|
-
|
294
|
-
|
295
|
-
|
296
|
-
Gemfile:
|
297
|
-
|
298
|
-
|
299
|
-
|
300
|
-
gem 'foo'
|
301
|
-
|
302
|
-
|
303
|
-
|
304
|
-
Gemfile.lock:
|
305
|
-
|
306
|
-
|
307
|
-
|
308
|
-
foo (1.4.3)
|
309
|
-
bar (~> 2.0)
|
310
|
-
bar (2.0.3)
|
311
|
-
|
312
|
-
|
313
|
-
|
314
|
-
Cases:
|
315
|
-
|
316
|
-
|
317
|
-
|
318
|
-
# Command Line Result
|
319
|
-
------------------------------------------------------------
|
320
|
-
1 bundle update --patch 'foo 1.4.5', 'bar 2.1.1'
|
321
|
-
2 bundle update --patch foo 'foo 1.4.5', 'bar 2.1.1'
|
322
|
-
3 bundle update --minor 'foo 1.5.1', 'bar 3.0.0'
|
323
|
-
4 bundle update --minor --strict 'foo 1.5.0', 'bar 2.1.1'
|
324
|
-
5 bundle update --patch --strict 'foo 1.4.4', 'bar 2.0.4'
|
325
|
-
|
326
|
-
|
327
|
-
|
328
|
-
In case 1, bar is upgraded to 2.1.1, a minor version increase, because
|
329
|
-
the dependency from foo 1.4.5 required it.
|
330
|
-
|
331
|
-
In case 2, only foo is requested to be unlocked, but bar is also
|
332
|
-
allowed to move because it's not a declared dependency in the Gemfile.
|
333
|
-
|
334
|
-
In case 3, bar goes up a whole major release, because a minor increase
|
335
|
-
is preferred now for foo, and when it goes to 1.5.1, it requires 3.0.0
|
336
|
-
of bar.
|
337
|
-
|
338
|
-
In case 4, foo is preferred up to a minor version, but 1.5.1 won't work
|
339
|
-
because the --strict flag removes bar 3.0.0 from consideration since
|
340
|
-
it's a major increment.
|
341
|
-
|
342
|
-
In case 5, both foo and bar have any minor or major increments removed
|
343
|
-
from consideration because of the --strict flag, so the most they can
|
344
|
-
move is up to 1.4.4 and 2.0.4.
|
345
|
-
|
346
|
-
RECOMMENDED WORKFLOW
|
347
|
-
In general, when working with an application managed with bundler, you
|
348
|
-
should use the following workflow:
|
349
|
-
|
350
|
-
o After you create your Gemfile(5) for the first time, run
|
351
|
-
|
352
|
-
$ bundle install
|
353
|
-
|
354
|
-
o Check the resulting Gemfile.lock into version control
|
355
|
-
|
356
|
-
$ git add Gemfile.lock
|
357
|
-
|
358
|
-
o When checking out this repository on another development machine,
|
359
|
-
run
|
360
|
-
|
361
|
-
$ bundle install
|
362
|
-
|
363
|
-
o When checking out this repository on a deployment machine, run
|
364
|
-
|
365
|
-
$ bundle install --deployment
|
366
|
-
|
367
|
-
o After changing the Gemfile(5) to reflect a new or update depen-
|
368
|
-
dency, run
|
369
|
-
|
370
|
-
$ bundle install
|
371
|
-
|
372
|
-
o Make sure to check the updated Gemfile.lock into version control
|
373
|
-
|
374
|
-
$ git add Gemfile.lock
|
375
|
-
|
376
|
-
o If bundle install(1) bundle-install.1.html reports a conflict, man-
|
377
|
-
ually update the specific gems that you changed in the Gemfile(5)
|
378
|
-
|
379
|
-
$ bundle update rails thin
|
380
|
-
|
381
|
-
o If you want to update all the gems to the latest possible versions
|
382
|
-
that still match the gems listed in the Gemfile(5), run
|
383
|
-
|
384
|
-
$ bundle update --all
|
385
|
-
|
386
|
-
|
387
|
-
|
388
|
-
|
389
|
-
|
390
|
-
|
391
|
-
December 2018 BUNDLE-UPDATE(1)
|