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