diff options
Diffstat (limited to 'man')
56 files changed, 212 insertions, 6422 deletions
diff --git a/man/bundle-add.1 b/man/bundle-add.1 deleted file mode 100644 index 486c249719..0000000000 --- a/man/bundle-add.1 +++ /dev/null @@ -1,66 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-ADD" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-add\fR \- Add gem to the Gemfile and run bundle install -. -.SH "SYNOPSIS" -\fBbundle add\fR \fIGEM_NAME\fR [\-\-group=GROUP] [\-\-version=VERSION] [\-\-source=SOURCE] [\-\-git=GIT] [\-\-branch=BRANCH] [\-\-skip\-install] [\-\-strict] [\-\-optimistic] -. -.SH "DESCRIPTION" -Adds the named gem to the Gemfile and run \fBbundle install\fR\. \fBbundle install\fR can be avoided by using the flag \fB\-\-skip\-install\fR\. -. -.P -Example: -. -.P -bundle add rails -. -.P -bundle add rails \-\-version "< 3\.0, > 1\.1" -. -.P -bundle add rails \-\-version "~> 5\.0\.0" \-\-source "https://gems\.example\.com" \-\-group "development" -. -.P -bundle add rails \-\-skip\-install -. -.P -bundle add rails \-\-group "development, test" -. -.SH "OPTIONS" -. -.TP -\fB\-\-version\fR, \fB\-v\fR -Specify version requirements(s) for the added gem\. -. -.TP -\fB\-\-group\fR, \fB\-g\fR -Specify the group(s) for the added gem\. Multiple groups should be separated by commas\. -. -.TP -\fB\-\-source\fR, , \fB\-s\fR -Specify the source for the added gem\. -. -.TP -\fB\-\-git\fR -Specify the git source for the added gem\. -. -.TP -\fB\-\-branch\fR -Specify the git branch for the added gem\. -. -.TP -\fB\-\-skip\-install\fR -Adds the gem to the Gemfile but does not install it\. -. -.TP -\fB\-\-optimistic\fR -Adds optimistic declaration of version -. -.TP -\fB\-\-strict\fR -Adds strict declaration of version - diff --git a/man/bundle-add.1.ronn b/man/bundle-add.1.ronn deleted file mode 100644 index 26cbe55647..0000000000 --- a/man/bundle-add.1.ronn +++ /dev/null @@ -1,46 +0,0 @@ -bundle-add(1) -- Add gem to the Gemfile and run bundle install -================================================================ - -## SYNOPSIS - -`bundle add` <GEM_NAME> [--group=GROUP] [--version=VERSION] [--source=SOURCE] [--git=GIT] [--branch=BRANCH] [--skip-install] [--strict] [--optimistic] - -## DESCRIPTION -Adds the named gem to the Gemfile and run `bundle install`. `bundle install` can be avoided by using the flag `--skip-install`. - -Example: - -bundle add rails - -bundle add rails --version "< 3.0, > 1.1" - -bundle add rails --version "~> 5.0.0" --source "https://gems.example.com" --group "development" - -bundle add rails --skip-install - -bundle add rails --group "development, test" - -## OPTIONS -* `--version`, `-v`: - Specify version requirements(s) for the added gem. - -* `--group`, `-g`: - Specify the group(s) for the added gem. Multiple groups should be separated by commas. - -* `--source`, , `-s`: - Specify the source for the added gem. - -* `--git`: - Specify the git source for the added gem. - -* `--branch`: - Specify the git branch for the added gem. - -* `--skip-install`: - Adds the gem to the Gemfile but does not install it. - -* `--optimistic`: - Adds optimistic declaration of version - -* `--strict`: - Adds strict declaration of version diff --git a/man/bundle-binstubs.1 b/man/bundle-binstubs.1 deleted file mode 100644 index 782a464c16..0000000000 --- a/man/bundle-binstubs.1 +++ /dev/null @@ -1,42 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-BINSTUBS" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-binstubs\fR \- Install the binstubs of the listed gems -. -.SH "SYNOPSIS" -\fBbundle binstubs\fR \fIGEM_NAME\fR [\-\-force] [\-\-path PATH] [\-\-standalone] -. -.SH "DESCRIPTION" -Binstubs are scripts that wrap around executables\. Bundler creates a small Ruby file (a binstub) that loads Bundler, runs the command, and puts it into \fBbin/\fR\. Binstubs are a shortcut\-or alternative\- to always using \fBbundle exec\fR\. This gives you a file that can be run directly, and one that will always run the correct gem version used by the application\. -. -.P -For example, if you run \fBbundle binstubs rspec\-core\fR, Bundler will create the file \fBbin/rspec\fR\. That file will contain enough code to load Bundler, tell it to load the bundled gems, and then run rspec\. -. -.P -This command generates binstubs for executables in \fBGEM_NAME\fR\. Binstubs are put into \fBbin\fR, or the \fB\-\-path\fR directory if one has been set\. Calling binstubs with [GEM [GEM]] will create binstubs for all given gems\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-force\fR -Overwrite existing binstubs if they exist\. -. -.TP -\fB\-\-path\fR -The location to install the specified binstubs to\. This defaults to \fBbin\fR\. -. -.TP -\fB\-\-standalone\fR -Makes binstubs that can work without depending on Rubygems or Bundler at runtime\. -. -.TP -\fB\-\-shebang\fR -Specify a different shebang executable name than the default (default \'ruby\') -. -.TP -\fB\-\-all\fR -Create binstubs for all gems in the bundle\. - diff --git a/man/bundle-binstubs.1.ronn b/man/bundle-binstubs.1.ronn deleted file mode 100644 index a96186929f..0000000000 --- a/man/bundle-binstubs.1.ronn +++ /dev/null @@ -1,41 +0,0 @@ -bundle-binstubs(1) -- Install the binstubs of the listed gems -============================================================= - -## SYNOPSIS - -`bundle binstubs` <GEM_NAME> [--force] [--path PATH] [--standalone] - -## DESCRIPTION - -Binstubs are scripts that wrap around executables. Bundler creates a -small Ruby file (a binstub) that loads Bundler, runs the command, -and puts it into `bin/`. Binstubs are a shortcut-or alternative- -to always using `bundle exec`. This gives you a file that can be run -directly, and one that will always run the correct gem version -used by the application. - -For example, if you run `bundle binstubs rspec-core`, Bundler will create -the file `bin/rspec`. That file will contain enough code to load Bundler, -tell it to load the bundled gems, and then run rspec. - -This command generates binstubs for executables in `GEM_NAME`. -Binstubs are put into `bin`, or the `--path` directory if one has been set. -Calling binstubs with [GEM [GEM]] will create binstubs for all given gems. - -## OPTIONS - -* `--force`: - Overwrite existing binstubs if they exist. - -* `--path`: - The location to install the specified binstubs to. This defaults to `bin`. - -* `--standalone`: - Makes binstubs that can work without depending on Rubygems or Bundler at - runtime. - -* `--shebang`: - Specify a different shebang executable name than the default (default 'ruby') - -* `--all`: - Create binstubs for all gems in the bundle. diff --git a/man/bundle-cache.1 b/man/bundle-cache.1 deleted file mode 100644 index f840893f96..0000000000 --- a/man/bundle-cache.1 +++ /dev/null @@ -1,55 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-CACHE" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-cache\fR \- Package your needed \fB\.gem\fR files into your application -. -.SH "SYNOPSIS" -\fBbundle cache\fR -. -.SH "DESCRIPTION" -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\. -. -.SH "GIT AND PATH GEMS" -The \fBbundle cache\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\. -. -.SH "SUPPORT FOR MULTIPLE PLATFORMS" -When using gems that have different packages for different platforms, Bundler supports caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \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\. -. -.SH "REMOTE FETCHING" -By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle cache(1) \fIbundle\-cache\.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\. -. -.P -For instance, consider this Gemfile(5): -. -.IP "" 4 -. -.nf - -source "https://rubygems\.org" - -gem "nokogiri" -. -.fi -. -.IP "" 0 -. -.P -If you run \fBbundle cache\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\. -. -.P -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\. -. -.P -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\. -. -.P -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\. -. -.P -One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle cache\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle cache\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\. -. -.P -By default, bundle cache(1) \fIbundle\-cache\.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 cache \-\-no\-install\fR\. diff --git a/man/bundle-cache.1.ronn b/man/bundle-cache.1.ronn deleted file mode 100644 index 383adb2ba3..0000000000 --- a/man/bundle-cache.1.ronn +++ /dev/null @@ -1,72 +0,0 @@ -bundle-cache(1) -- Package your needed `.gem` files into your application -=========================================================================== - -## SYNOPSIS - -`bundle cache` - -## DESCRIPTION - -Copy all of the `.gem` files needed to run the application into the -`vendor/cache` directory. In the future, when running [bundle install(1)][bundle-install], -use the gems in the cache in preference to the ones on `rubygems.org`. - -## GIT AND PATH GEMS - -The `bundle cache` command can also package `:git` and `:path` dependencies -besides .gem files. This needs to be explicitly enabled via the `--all` option. -Once used, the `--all` option will be remembered. - -## SUPPORT FOR MULTIPLE PLATFORMS - -When using gems that have different packages for different platforms, Bundler -supports caching of gems for other platforms where the Gemfile has been resolved -(i.e. present in the lockfile) in `vendor/cache`. This needs to be enabled via -the `--all-platforms` option. This setting will be remembered in your local -bundler configuration. - -## REMOTE FETCHING - -By default, if you run `bundle install(1)`](bundle-install.1.html) after running -[bundle cache(1)](bundle-cache.1.html), bundler will still connect to `rubygems.org` -to check whether a platform-specific gem exists for any of the gems -in `vendor/cache`. - -For instance, consider this Gemfile(5): - - source "https://rubygems.org" - - gem "nokogiri" - -If you run `bundle cache` under C Ruby, bundler will retrieve -the version of `nokogiri` for the `"ruby"` platform. If you deploy -to JRuby and run `bundle install`, bundler is forced to check to -see whether a `"java"` platformed `nokogiri` exists. - -Even though the `nokogiri` gem for the Ruby platform is -_technically_ acceptable on JRuby, it has a C extension -that does not run on JRuby. As a result, bundler will, by default, -still connect to `rubygems.org` to check whether it has a version -of one of your gems more specific to your platform. - -This problem is also not limited to the `"java"` platform. -A similar (common) problem can happen when developing on Windows -and deploying to Linux, or even when developing on OSX and -deploying to Linux. - -If you know for sure that the gems packaged in `vendor/cache` -are appropriate for the platform you are on, you can run -`bundle install --local` to skip checking for more appropriate -gems, and use the ones in `vendor/cache`. - -One way to be sure that you have the right platformed versions -of all your gems is to run `bundle cache` on an identical -machine and check in the gems. For instance, you can run -`bundle cache` on an identical staging box during your -staging process, and check in the `vendor/cache` before -deploying to production. - -By default, [bundle cache(1)](bundle-cache.1.html) fetches and also -installs the gems to the default location. To package the -dependencies to `vendor/cache` without installing them to the -local install location, you can run `bundle cache --no-install`. diff --git a/man/bundle-check.1 b/man/bundle-check.1 deleted file mode 100644 index 4c7bc3f329..0000000000 --- a/man/bundle-check.1 +++ /dev/null @@ -1,31 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-CHECK" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-check\fR \- Verifies if dependencies are satisfied by installed gems -. -.SH "SYNOPSIS" -\fBbundle check\fR [\-\-dry\-run] [\-\-gemfile=FILE] [\-\-path=PATH] -. -.SH "DESCRIPTION" -\fBcheck\fR searches the local machine for each of the gems requested in the Gemfile\. If all gems are found, Bundler prints a success message and exits with a status of 0\. -. -.P -If not, the first missing gem is listed and Bundler exits status 1\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-dry\-run\fR -Locks the [\fBGemfile(5)\fR][Gemfile(5)] before running the command\. -. -.TP -\fB\-\-gemfile\fR -Use the specified gemfile instead of the [\fBGemfile(5)\fR][Gemfile(5)]\. -. -.TP -\fB\-\-path\fR -Specify a different path than the system default (\fB$BUNDLE_PATH\fR or \fB$GEM_HOME\fR)\. Bundler will remember this value for future installs on this machine\. - diff --git a/man/bundle-check.1.ronn b/man/bundle-check.1.ronn deleted file mode 100644 index f2846b8ff2..0000000000 --- a/man/bundle-check.1.ronn +++ /dev/null @@ -1,26 +0,0 @@ -bundle-check(1) -- Verifies if dependencies are satisfied by installed gems -=========================================================================== - -## SYNOPSIS - -`bundle check` [--dry-run] - [--gemfile=FILE] - [--path=PATH] - -## DESCRIPTION - -`check` searches the local machine for each of the gems requested in the -Gemfile. If all gems are found, Bundler prints a success message and exits with -a status of 0. - -If not, the first missing gem is listed and Bundler exits status 1. - -## OPTIONS - -* `--dry-run`: - Locks the [`Gemfile(5)`][Gemfile(5)] before running the command. -* `--gemfile`: - Use the specified gemfile instead of the [`Gemfile(5)`][Gemfile(5)]. -* `--path`: - Specify a different path than the system default (`$BUNDLE_PATH` or `$GEM_HOME`). - Bundler will remember this value for future installs on this machine. diff --git a/man/bundle-clean.1 b/man/bundle-clean.1 deleted file mode 100644 index dd1682a48b..0000000000 --- a/man/bundle-clean.1 +++ /dev/null @@ -1,24 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-CLEAN" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-clean\fR \- Cleans up unused gems in your bundler directory -. -.SH "SYNOPSIS" -\fBbundle clean\fR [\-\-dry\-run] [\-\-force] -. -.SH "DESCRIPTION" -This command will remove all unused gems in your bundler directory\. This is useful when you have made many changes to your gem dependencies\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-dry\-run\fR -Print the changes, but do not clean the unused gems\. -. -.TP -\fB\-\-force\fR -Force a clean even if \fB\-\-path\fR is not set\. - diff --git a/man/bundle-clean.1.ronn b/man/bundle-clean.1.ronn deleted file mode 100644 index de23991782..0000000000 --- a/man/bundle-clean.1.ronn +++ /dev/null @@ -1,18 +0,0 @@ -bundle-clean(1) -- Cleans up unused gems in your bundler directory -================================================================== - -## SYNOPSIS - -`bundle clean` [--dry-run] [--force] - -## DESCRIPTION - -This command will remove all unused gems in your bundler directory. This is -useful when you have made many changes to your gem dependencies. - -## OPTIONS - -* `--dry-run`: - Print the changes, but do not clean the unused gems. -* `--force`: - Force a clean even if `--path` is not set. diff --git a/man/bundle-config.1 b/man/bundle-config.1 deleted file mode 100644 index d989aaeb86..0000000000 --- a/man/bundle-config.1 +++ /dev/null @@ -1,491 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-CONFIG" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-config\fR \- Set bundler configuration options -. -.SH "SYNOPSIS" -\fBbundle config\fR [list|get|set|unset] [\fIname\fR [\fIvalue\fR]] -. -.SH "DESCRIPTION" -This command allows you to interact with Bundler\'s configuration system\. -. -.P -Bundler loads configuration settings in this order: -. -.IP "1." 4 -Local config (\fB<project_root>/\.bundle/config\fR or \fB$BUNDLE_APP_CONFIG/config\fR) -. -.IP "2." 4 -Environmental variables (\fBENV\fR) -. -.IP "3." 4 -Global config (\fB~/\.bundle/config\fR) -. -.IP "4." 4 -Bundler default config -. -.IP "" 0 -. -.P -Executing \fBbundle config list\fR with will print a list of all bundler configuration for the current bundle, and where that configuration was set\. -. -.P -Executing \fBbundle config get <name>\fR will print the value of that configuration setting, and where it was set\. -. -.P -Executing \fBbundle config set <name> <value>\fR will set that configuration to the value specified for all bundles executed as the current user\. The configuration will be stored in \fB~/\.bundle/config\fR\. If \fIname\fR already is set, \fIname\fR will be overridden and user will be warned\. -. -.P -Executing \fBbundle config set \-\-global <name> <value>\fR works the same as above\. -. -.P -Executing \fBbundle config set \-\-local <name> <value>\fR will set that configuration in the directory for the local application\. The configuration will be stored in \fB<project_root>/\.bundle/config\fR\. If \fBBUNDLE_APP_CONFIG\fR is set, the configuration will be stored in \fB$BUNDLE_APP_CONFIG/config\fR\. -. -.P -Executing \fBbundle config unset <name>\fR will delete the configuration in both local and global sources\. -. -.P -Executing \fBbundle config unset \-\-global <name>\fR will delete the configuration only from the user configuration\. -. -.P -Executing \fBbundle config unset \-\-local <name> <value>\fR will delete the configuration only from the local application\. -. -.P -Executing bundle with the \fBBUNDLE_IGNORE_CONFIG\fR environment variable set will cause it to ignore all configuration\. -. -.P -Executing \fBbundle config set \-\-local disable_multisource true\fR upgrades the warning about the Gemfile containing multiple primary sources to an error\. Executing \fBbundle config unset disable_multisource\fR downgrades this error to a warning\. -. -.SH "REMEMBERING OPTIONS" -Flags passed to \fBbundle install\fR or the Bundler runtime, such as \fB\-\-path foo\fR or \fB\-\-without production\fR, are remembered between commands and saved to your local application\'s configuration (normally, \fB\./\.bundle/config\fR)\. -. -.P -However, this will be changed in bundler 3, so it\'s better not to rely on this behavior\. If these options must be remembered, it\'s better to set them using \fBbundle config\fR (e\.g\., \fBbundle config set \-\-local path foo\fR)\. -. -.P -The options that can be configured are: -. -.TP -\fBbin\fR -Creates a directory (defaults to \fB~/bin\fR) and place any executables from the gem there\. These executables run in Bundler\'s context\. If used, you might add this directory to your environment\'s \fBPATH\fR variable\. For instance, if the \fBrails\fR gem comes with a \fBrails\fR executable, this flag will create a \fBbin/rails\fR executable that ensures that all referred dependencies will be resolved using the bundled gems\. -. -.TP -\fBdeployment\fR -In deployment mode, Bundler will \'roll\-out\' the bundle for \fBproduction\fR use\. Please check carefully if you want to have this option enabled in \fBdevelopment\fR or \fBtest\fR environments\. -. -.TP -\fBpath\fR -The location to install the specified gems to\. This defaults to Rubygems\' setting\. Bundler shares this location with Rubygems, \fBgem install \.\.\.\fR will have gem installed there, too\. Therefore, gems installed without a \fB\-\-path \.\.\.\fR setting will show up by calling \fBgem list\fR\. Accordingly, gems installed to other locations will not get listed\. -. -.TP -\fBwithout\fR -A space\-separated list of groups referencing gems to skip during installation\. -. -.TP -\fBwith\fR -A space\-separated list of groups referencing gems to include during installation\. -. -.SH "BUILD OPTIONS" -You can use \fBbundle config\fR to give Bundler the flags to pass to the gem installer every time bundler tries to install a particular gem\. -. -.P -A very common example, the \fBmysql\fR gem, requires Snow Leopard users to pass configuration flags to \fBgem install\fR to specify where to find the \fBmysql_config\fR executable\. -. -.IP "" 4 -. -.nf - -gem install mysql \-\- \-\-with\-mysql\-config=/usr/local/mysql/bin/mysql_config -. -.fi -. -.IP "" 0 -. -.P -Since the specific location of that executable can change from machine to machine, you can specify these flags on a per\-machine basis\. -. -.IP "" 4 -. -.nf - -bundle config set \-\-global build\.mysql \-\-with\-mysql\-config=/usr/local/mysql/bin/mysql_config -. -.fi -. -.IP "" 0 -. -.P -After running this command, every time bundler needs to install the \fBmysql\fR gem, it will pass along the flags you specified\. -. -.SH "CONFIGURATION KEYS" -Configuration keys in bundler have two forms: the canonical form and the environment variable form\. -. -.P -For instance, passing the \fB\-\-without\fR flag to bundle install(1) \fIbundle\-install\.1\.html\fR prevents Bundler from installing certain groups specified in the Gemfile(5)\. Bundler persists this value in \fBapp/\.bundle/config\fR so that calls to \fBBundler\.setup\fR do not try to find gems from the \fBGemfile\fR that you didn\'t install\. Additionally, subsequent calls to bundle install(1) \fIbundle\-install\.1\.html\fR remember this setting and skip those groups\. -. -.P -The canonical form of this configuration is \fB"without"\fR\. To convert the canonical form to the environment variable form, capitalize it, and prepend \fBBUNDLE_\fR\. The environment variable form of \fB"without"\fR is \fBBUNDLE_WITHOUT\fR\. -. -.P -Any periods in the configuration keys must be replaced with two underscores when setting it via environment variables\. The configuration key \fBlocal\.rack\fR becomes the environment variable \fBBUNDLE_LOCAL__RACK\fR\. -. -.SH "LIST OF AVAILABLE KEYS" -The following is a list of all configuration keys and their purpose\. You can learn more about their operation in bundle install(1) \fIbundle\-install\.1\.html\fR\. -. -.IP "\(bu" 4 -\fBallow_bundler_dependency_conflicts\fR (\fBBUNDLE_ALLOW_BUNDLER_DEPENDENCY_CONFLICTS\fR): Allow resolving to specifications that have dependencies on \fBbundler\fR that are incompatible with the running Bundler version\. -. -.IP "\(bu" 4 -\fBallow_deployment_source_credential_changes\fR (\fBBUNDLE_ALLOW_DEPLOYMENT_SOURCE_CREDENTIAL_CHANGES\fR): When in deployment mode, allow changing the credentials to a gem\'s source\. Ex: \fBhttps://some\.host\.com/gems/path/\fR \-> \fBhttps://user_name:password@some\.host\.com/gems/path\fR -. -.IP "\(bu" 4 -\fBallow_offline_install\fR (\fBBUNDLE_ALLOW_OFFLINE_INSTALL\fR): Allow Bundler to use cached data when installing without network access\. -. -.IP "\(bu" 4 -\fBauto_clean_without_path\fR (\fBBUNDLE_AUTO_CLEAN_WITHOUT_PATH\fR): Automatically run \fBbundle clean\fR after installing when an explicit \fBpath\fR has not been set and Bundler is not installing into the system gems\. -. -.IP "\(bu" 4 -\fBauto_install\fR (\fBBUNDLE_AUTO_INSTALL\fR): Automatically run \fBbundle install\fR when gems are missing\. -. -.IP "\(bu" 4 -\fBbin\fR (\fBBUNDLE_BIN\fR): Install executables from gems in the bundle to the specified directory\. Defaults to \fBfalse\fR\. -. -.IP "\(bu" 4 -\fBcache_all\fR (\fBBUNDLE_CACHE_ALL\fR): Cache all gems, including path and git gems\. This needs to be explicitly configured on bundler 1 and bundler 2, but will be the default on bundler 3\. -. -.IP "\(bu" 4 -\fBcache_all_platforms\fR (\fBBUNDLE_CACHE_ALL_PLATFORMS\fR): Cache gems for all platforms\. -. -.IP "\(bu" 4 -\fBcache_path\fR (\fBBUNDLE_CACHE_PATH\fR): The directory that bundler will place cached gems in when running \fBbundle package\fR, and that bundler will look in when installing gems\. Defaults to \fBvendor/cache\fR\. -. -.IP "\(bu" 4 -\fBclean\fR (\fBBUNDLE_CLEAN\fR): Whether Bundler should run \fBbundle clean\fR automatically after \fBbundle install\fR\. -. -.IP "\(bu" 4 -\fBconsole\fR (\fBBUNDLE_CONSOLE\fR): The console that \fBbundle console\fR starts\. Defaults to \fBirb\fR\. -. -.IP "\(bu" 4 -\fBdefault_install_uses_path\fR (\fBBUNDLE_DEFAULT_INSTALL_USES_PATH\fR): Whether a \fBbundle install\fR without an explicit \fB\-\-path\fR argument defaults to installing gems in \fB\.bundle\fR\. -. -.IP "\(bu" 4 -\fBdeployment\fR (\fBBUNDLE_DEPLOYMENT\fR): Disallow changes to the \fBGemfile\fR\. When the \fBGemfile\fR is changed and the lockfile has not been updated, running Bundler commands will be blocked\. -. -.IP "\(bu" 4 -\fBdisable_checksum_validation\fR (\fBBUNDLE_DISABLE_CHECKSUM_VALIDATION\fR): Allow installing gems even if they do not match the checksum provided by RubyGems\. -. -.IP "\(bu" 4 -\fBdisable_exec_load\fR (\fBBUNDLE_DISABLE_EXEC_LOAD\fR): Stop Bundler from using \fBload\fR to launch an executable in\-process in \fBbundle exec\fR\. -. -.IP "\(bu" 4 -\fBdisable_local_branch_check\fR (\fBBUNDLE_DISABLE_LOCAL_BRANCH_CHECK\fR): Allow Bundler to use a local git override without a branch specified in the Gemfile\. -. -.IP "\(bu" 4 -\fBdisable_multisource\fR (\fBBUNDLE_DISABLE_MULTISOURCE\fR): When set, Gemfiles containing multiple sources will produce errors instead of warnings\. Use \fBbundle config unset disable_multisource\fR to unset\. -. -.IP "\(bu" 4 -\fBdisable_shared_gems\fR (\fBBUNDLE_DISABLE_SHARED_GEMS\fR): Stop Bundler from accessing gems installed to RubyGems\' normal location\. -. -.IP "\(bu" 4 -\fBdisable_version_check\fR (\fBBUNDLE_DISABLE_VERSION_CHECK\fR): Stop Bundler from checking if a newer Bundler version is available on rubygems\.org\. -. -.IP "\(bu" 4 -\fBforce_ruby_platform\fR (\fBBUNDLE_FORCE_RUBY_PLATFORM\fR): Ignore the current machine\'s platform and install only \fBruby\fR platform gems\. As a result, gems with native extensions will be compiled from source\. -. -.IP "\(bu" 4 -\fBfrozen\fR (\fBBUNDLE_FROZEN\fR): Disallow changes to the \fBGemfile\fR\. When the \fBGemfile\fR is changed and the lockfile has not been updated, running Bundler commands will be blocked\. Defaults to \fBtrue\fR when \fB\-\-deployment\fR is used\. -. -.IP "\(bu" 4 -\fBgem\.push_key\fR (\fBBUNDLE_GEM__PUSH_KEY\fR): Sets the \fB\-\-key\fR parameter for \fBgem push\fR when using the \fBrake release\fR command with a private gemstash server\. -. -.IP "\(bu" 4 -\fBgemfile\fR (\fBBUNDLE_GEMFILE\fR): The name of the file that bundler should use as the \fBGemfile\fR\. This location of this file also sets the root of the project, which is used to resolve relative paths in the \fBGemfile\fR, among other things\. By default, bundler will search up from the current working directory until it finds a \fBGemfile\fR\. -. -.IP "\(bu" 4 -\fBglobal_gem_cache\fR (\fBBUNDLE_GLOBAL_GEM_CACHE\fR): Whether Bundler should cache all gems globally, rather than locally to the installing Ruby installation\. -. -.IP "\(bu" 4 -\fBignore_messages\fR (\fBBUNDLE_IGNORE_MESSAGES\fR): When set, no post install messages will be printed\. To silence a single gem, use dot notation like \fBignore_messages\.httparty true\fR\. -. -.IP "\(bu" 4 -\fBinit_gems_rb\fR (\fBBUNDLE_INIT_GEMS_RB\fR) Generate a \fBgems\.rb\fR instead of a \fBGemfile\fR when running \fBbundle init\fR\. -. -.IP "\(bu" 4 -\fBjobs\fR (\fBBUNDLE_JOBS\fR): The number of gems Bundler can install in parallel\. Defaults to 1\. -. -.IP "\(bu" 4 -\fBno_install\fR (\fBBUNDLE_NO_INSTALL\fR): Whether \fBbundle package\fR should skip installing gems\. -. -.IP "\(bu" 4 -\fBno_prune\fR (\fBBUNDLE_NO_PRUNE\fR): Whether Bundler should leave outdated gems unpruned when caching\. -. -.IP "\(bu" 4 -\fBonly_update_to_newer_versions\fR (\fBBUNDLE_ONLY_UPDATE_TO_NEWER_VERSIONS\fR): During \fBbundle update\fR, only resolve to newer versions of the gems in the lockfile\. -. -.IP "\(bu" 4 -\fBpath\fR (\fBBUNDLE_PATH\fR): The location on disk where all gems in your bundle will be located regardless of \fB$GEM_HOME\fR or \fB$GEM_PATH\fR values\. Bundle gems not found in this location will be installed by \fBbundle install\fR\. Defaults to \fBGem\.dir\fR\. When \-\-deployment is used, defaults to vendor/bundle\. -. -.IP "\(bu" 4 -\fBpath\.system\fR (\fBBUNDLE_PATH__SYSTEM\fR): Whether Bundler will install gems into the default system path (\fBGem\.dir\fR)\. -. -.IP "\(bu" 4 -\fBpath_relative_to_cwd\fR (\fBBUNDLE_PATH_RELATIVE_TO_CWD\fR) Makes \fB\-\-path\fR relative to the CWD instead of the \fBGemfile\fR\. -. -.IP "\(bu" 4 -\fBplugins\fR (\fBBUNDLE_PLUGINS\fR): Enable Bundler\'s experimental plugin system\. -. -.IP "\(bu" 4 -\fBprefer_patch\fR (BUNDLE_PREFER_PATCH): Prefer updating only to next patch version during updates\. Makes \fBbundle update\fR calls equivalent to \fBbundler update \-\-patch\fR\. -. -.IP "\(bu" 4 -\fBprint_only_version_number\fR (\fBBUNDLE_PRINT_ONLY_VERSION_NUMBER\fR) Print only version number from \fBbundler \-\-version\fR\. -. -.IP "\(bu" 4 -\fBredirect\fR (\fBBUNDLE_REDIRECT\fR): The number of redirects allowed for network requests\. Defaults to \fB5\fR\. -. -.IP "\(bu" 4 -\fBretry\fR (\fBBUNDLE_RETRY\fR): The number of times to retry failed network requests\. Defaults to \fB3\fR\. -. -.IP "\(bu" 4 -\fBsetup_makes_kernel_gem_public\fR (\fBBUNDLE_SETUP_MAKES_KERNEL_GEM_PUBLIC\fR): Have \fBBundler\.setup\fR make the \fBKernel#gem\fR method public, even though RubyGems declares it as private\. -. -.IP "\(bu" 4 -\fBshebang\fR (\fBBUNDLE_SHEBANG\fR): The program name that should be invoked for generated binstubs\. Defaults to the ruby install name used to generate the binstub\. -. -.IP "\(bu" 4 -\fBsilence_deprecations\fR (\fBBUNDLE_SILENCE_DEPRECATIONS\fR): Whether Bundler should silence deprecation warnings for behavior that will be changed in the next major version\. -. -.IP "\(bu" 4 -\fBsilence_root_warning\fR (\fBBUNDLE_SILENCE_ROOT_WARNING\fR): Silence the warning Bundler prints when installing gems as root\. -. -.IP "\(bu" 4 -\fBspecific_platform\fR (\fBBUNDLE_SPECIFIC_PLATFORM\fR): Allow bundler to resolve for the specific running platform and store it in the lockfile, instead of only using a generic platform\. A specific platform is the exact platform triple reported by \fBGem::Platform\.local\fR, such as \fBx86_64\-darwin\-16\fR or \fBuniversal\-java\-1\.8\fR\. On the other hand, generic platforms are those such as \fBruby\fR, \fBmswin\fR, or \fBjava\fR\. In this example, \fBx86_64\-darwin\-16\fR would map to \fBruby\fR and \fBuniversal\-java\-1\.8\fR to \fBjava\fR\. -. -.IP "\(bu" 4 -\fBssl_ca_cert\fR (\fBBUNDLE_SSL_CA_CERT\fR): Path to a designated CA certificate file or folder containing multiple certificates for trusted CAs in PEM format\. -. -.IP "\(bu" 4 -\fBssl_client_cert\fR (\fBBUNDLE_SSL_CLIENT_CERT\fR): Path to a designated file containing a X\.509 client certificate and key in PEM format\. -. -.IP "\(bu" 4 -\fBssl_verify_mode\fR (\fBBUNDLE_SSL_VERIFY_MODE\fR): The SSL verification mode Bundler uses when making HTTPS requests\. Defaults to verify peer\. -. -.IP "\(bu" 4 -\fBsuppress_install_using_messages\fR (\fBBUNDLE_SUPPRESS_INSTALL_USING_MESSAGES\fR): Avoid printing \fBUsing \.\.\.\fR messages during installation when the version of a gem has not changed\. -. -.IP "\(bu" 4 -\fBsystem_bindir\fR (\fBBUNDLE_SYSTEM_BINDIR\fR): The location where RubyGems installs binstubs\. Defaults to \fBGem\.bindir\fR\. -. -.IP "\(bu" 4 -\fBtimeout\fR (\fBBUNDLE_TIMEOUT\fR): The seconds allowed before timing out for network requests\. Defaults to \fB10\fR\. -. -.IP "\(bu" 4 -\fBunlock_source_unlocks_spec\fR (\fBBUNDLE_UNLOCK_SOURCE_UNLOCKS_SPEC\fR): Whether running \fBbundle update \-\-source NAME\fR unlocks a gem with the given name\. Defaults to \fBtrue\fR\. -. -.IP "\(bu" 4 -\fBupdate_requires_all_flag\fR (\fBBUNDLE_UPDATE_REQUIRES_ALL_FLAG\fR) Require passing \fB\-\-all\fR to \fBbundle update\fR when everything should be updated, and disallow passing no options to \fBbundle update\fR\. -. -.IP "\(bu" 4 -\fBuser_agent\fR (\fBBUNDLE_USER_AGENT\fR): The custom user agent fragment Bundler includes in API requests\. -. -.IP "\(bu" 4 -\fBwith\fR (\fBBUNDLE_WITH\fR): A \fB:\fR\-separated list of groups whose gems bundler should install\. -. -.IP "\(bu" 4 -\fBwithout\fR (\fBBUNDLE_WITHOUT\fR): A \fB:\fR\-separated list of groups whose gems bundler should not install\. -. -.IP "" 0 -. -.P -In general, you should set these settings per\-application by using the applicable flag to the bundle install(1) \fIbundle\-install\.1\.html\fR or bundle package(1) \fIbundle\-package\.1\.html\fR command\. -. -.P -You can set them globally either via environment variables or \fBbundle config\fR, whichever is preferable for your setup\. If you use both, environment variables will take preference over global settings\. -. -.SH "LOCAL GIT REPOS" -Bundler also allows you to work against a git repository locally instead of using the remote version\. This can be achieved by setting up a local override: -. -.IP "" 4 -. -.nf - -bundle config set \-\-local local\.GEM_NAME /path/to/local/git/repository -. -.fi -. -.IP "" 0 -. -.P -For example, in order to use a local Rack repository, a developer could call: -. -.IP "" 4 -. -.nf - -bundle config set \-\-local local\.rack ~/Work/git/rack -. -.fi -. -.IP "" 0 -. -.P -Now instead of checking out the remote git repository, the local override will be used\. Similar to a path source, every time the local git repository change, changes will be automatically picked up by Bundler\. This means a commit in the local git repo will update the revision in the \fBGemfile\.lock\fR to the local git repo revision\. This requires the same attention as git submodules\. Before pushing to the remote, you need to ensure the local override was pushed, otherwise you may point to a commit that only exists in your local machine\. You\'ll also need to CGI escape your usernames and passwords as well\. -. -.P -Bundler does many checks to ensure a developer won\'t work with invalid references\. Particularly, we force a developer to specify a branch in the \fBGemfile\fR in order to use this feature\. If the branch specified in the \fBGemfile\fR and the current branch in the local git repository do not match, Bundler will abort\. This ensures that a developer is always working against the correct branches, and prevents accidental locking to a different branch\. -. -.P -Finally, Bundler also ensures that the current revision in the \fBGemfile\.lock\fR exists in the local git repository\. By doing this, Bundler forces you to fetch the latest changes in the remotes\. -. -.SH "MIRRORS OF GEM SOURCES" -Bundler supports overriding gem sources with mirrors\. This allows you to configure rubygems\.org as the gem source in your Gemfile while still using your mirror to fetch gems\. -. -.IP "" 4 -. -.nf - -bundle config set \-\-global mirror\.SOURCE_URL MIRROR_URL -. -.fi -. -.IP "" 0 -. -.P -For example, to use a mirror of rubygems\.org hosted at rubygems\-mirror\.org: -. -.IP "" 4 -. -.nf - -bundle config set \-\-global mirror\.http://rubygems\.org http://rubygems\-mirror\.org -. -.fi -. -.IP "" 0 -. -.P -Each mirror also provides a fallback timeout setting\. If the mirror does not respond within the fallback timeout, Bundler will try to use the original server instead of the mirror\. -. -.IP "" 4 -. -.nf - -bundle config set \-\-global mirror\.SOURCE_URL\.fallback_timeout TIMEOUT -. -.fi -. -.IP "" 0 -. -.P -For example, to fall back to rubygems\.org after 3 seconds: -. -.IP "" 4 -. -.nf - -bundle config set \-\-global mirror\.https://rubygems\.org\.fallback_timeout 3 -. -.fi -. -.IP "" 0 -. -.P -The default fallback timeout is 0\.1 seconds, but the setting can currently only accept whole seconds (for example, 1, 15, or 30)\. -. -.SH "CREDENTIALS FOR GEM SOURCES" -Bundler allows you to configure credentials for any gem source, which allows you to avoid putting secrets into your Gemfile\. -. -.IP "" 4 -. -.nf - -bundle config set \-\-global SOURCE_HOSTNAME USERNAME:PASSWORD -. -.fi -. -.IP "" 0 -. -.P -For example, to save the credentials of user \fBclaudette\fR for the gem source at \fBgems\.longerous\.com\fR, you would run: -. -.IP "" 4 -. -.nf - -bundle config set \-\-global gems\.longerous\.com claudette:s00pers3krit -. -.fi -. -.IP "" 0 -. -.P -Or you can set the credentials as an environment variable like this: -. -.IP "" 4 -. -.nf - -export BUNDLE_GEMS__LONGEROUS__COM="claudette:s00pers3krit" -. -.fi -. -.IP "" 0 -. -.P -For gems with a git source with HTTP(S) URL you can specify credentials like so: -. -.IP "" 4 -. -.nf - -bundle config set \-\-global https://github\.com/bundler/bundler\.git username:password -. -.fi -. -.IP "" 0 -. -.P -Or you can set the credentials as an environment variable like so: -. -.IP "" 4 -. -.nf - -export BUNDLE_GITHUB__COM=username:password -. -.fi -. -.IP "" 0 -. -.P -This is especially useful for private repositories on hosts such as Github, where you can use personal OAuth tokens: -. -.IP "" 4 -. -.nf - -export BUNDLE_GITHUB__COM=abcd0123generatedtoken:x\-oauth\-basic -. -.fi -. -.IP "" 0 -. -.SH "CONFIGURE BUNDLER DIRECTORIES" -Bundler\'s home, config, cache and plugin directories are able to be configured through environment variables\. The default location for Bundler\'s home directory is \fB~/\.bundle\fR, which all directories inherit from by default\. The following outlines the available environment variables and their default values -. -.IP "" 4 -. -.nf - -BUNDLE_USER_HOME : $HOME/\.bundle -BUNDLE_USER_CACHE : $BUNDLE_USER_HOME/cache -BUNDLE_USER_CONFIG : $BUNDLE_USER_HOME/config -BUNDLE_USER_PLUGIN : $BUNDLE_USER_HOME/plugin -. -.fi -. -.IP "" 0 - diff --git a/man/bundle-config.1.ronn b/man/bundle-config.1.ronn deleted file mode 100644 index a0ff30cb15..0000000000 --- a/man/bundle-config.1.ronn +++ /dev/null @@ -1,396 +0,0 @@ -bundle-config(1) -- Set bundler configuration options -===================================================== - -## SYNOPSIS - -`bundle config` [list|get|set|unset] [<name> [<value>]] - -## DESCRIPTION - -This command allows you to interact with Bundler's configuration system. - -Bundler loads configuration settings in this order: - -1. Local config (`<project_root>/.bundle/config` or `$BUNDLE_APP_CONFIG/config`) -2. Environmental variables (`ENV`) -3. Global config (`~/.bundle/config`) -4. Bundler default config - -Executing `bundle config list` with will print a list of all bundler -configuration for the current bundle, and where that configuration -was set. - -Executing `bundle config get <name>` will print the value of that configuration -setting, and where it was set. - -Executing `bundle config set <name> <value>` will set that configuration to the -value specified for all bundles executed as the current user. The configuration -will be stored in `~/.bundle/config`. If <name> already is set, <name> will be -overridden and user will be warned. - -Executing `bundle config set --global <name> <value>` works the same as above. - -Executing `bundle config set --local <name> <value>` will set that configuration -in the directory for the local application. The configuration will be stored in -`<project_root>/.bundle/config`. If `BUNDLE_APP_CONFIG` is set, the configuration -will be stored in `$BUNDLE_APP_CONFIG/config`. - -Executing `bundle config unset <name>` will delete the configuration in both -local and global sources. - -Executing `bundle config unset --global <name>` will delete the configuration -only from the user configuration. - -Executing `bundle config unset --local <name> <value>` will delete the -configuration only from the local application. - -Executing bundle with the `BUNDLE_IGNORE_CONFIG` environment variable set will -cause it to ignore all configuration. - -Executing `bundle config set --local disable_multisource true` upgrades the warning about -the Gemfile containing multiple primary sources to an error. Executing `bundle -config unset disable_multisource` downgrades this error to a warning. - -## REMEMBERING OPTIONS - -Flags passed to `bundle install` or the Bundler runtime, such as `--path foo` or -`--without production`, are remembered between commands and saved to your local -application's configuration (normally, `./.bundle/config`). - -However, this will be changed in bundler 3, so it's better not to rely on this -behavior. If these options must be remembered, it's better to set them using -`bundle config` (e.g., `bundle config set --local path foo`). - -The options that can be configured are: - -* `bin`: - Creates a directory (defaults to `~/bin`) and place any executables from the - gem there. These executables run in Bundler's context. If used, you might add - this directory to your environment's `PATH` variable. For instance, if the - `rails` gem comes with a `rails` executable, this flag will create a - `bin/rails` executable that ensures that all referred dependencies will be - resolved using the bundled gems. - -* `deployment`: - In deployment mode, Bundler will 'roll-out' the bundle for - `production` use. Please check carefully if you want to have this option - enabled in `development` or `test` environments. - -* `path`: - The location to install the specified gems to. This defaults to Rubygems' - setting. Bundler shares this location with Rubygems, `gem install ...` will - have gem installed there, too. Therefore, gems installed without a - `--path ...` setting will show up by calling `gem list`. Accordingly, gems - installed to other locations will not get listed. - -* `without`: - A space-separated list of groups referencing gems to skip during installation. - -* `with`: - A space-separated list of groups referencing gems to include during installation. - -## BUILD OPTIONS - -You can use `bundle config` to give Bundler the flags to pass to the gem -installer every time bundler tries to install a particular gem. - -A very common example, the `mysql` gem, requires Snow Leopard users to -pass configuration flags to `gem install` to specify where to find the -`mysql_config` executable. - - gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config - -Since the specific location of that executable can change from machine -to machine, you can specify these flags on a per-machine basis. - - bundle config set --global build.mysql --with-mysql-config=/usr/local/mysql/bin/mysql_config - -After running this command, every time bundler needs to install the -`mysql` gem, it will pass along the flags you specified. - -## CONFIGURATION KEYS - -Configuration keys in bundler have two forms: the canonical form and the -environment variable form. - -For instance, passing the `--without` flag to [bundle install(1)](bundle-install.1.html) -prevents Bundler from installing certain groups specified in the Gemfile(5). Bundler -persists this value in `app/.bundle/config` so that calls to `Bundler.setup` -do not try to find gems from the `Gemfile` that you didn't install. Additionally, -subsequent calls to [bundle install(1)](bundle-install.1.html) remember this setting -and skip those groups. - -The canonical form of this configuration is `"without"`. To convert the canonical -form to the environment variable form, capitalize it, and prepend `BUNDLE_`. The -environment variable form of `"without"` is `BUNDLE_WITHOUT`. - -Any periods in the configuration keys must be replaced with two underscores when -setting it via environment variables. The configuration key `local.rack` becomes -the environment variable `BUNDLE_LOCAL__RACK`. - -## LIST OF AVAILABLE KEYS - -The following is a list of all configuration keys and their purpose. You can -learn more about their operation in [bundle install(1)](bundle-install.1.html). - -* `allow_bundler_dependency_conflicts` (`BUNDLE_ALLOW_BUNDLER_DEPENDENCY_CONFLICTS`): - Allow resolving to specifications that have dependencies on `bundler` that - are incompatible with the running Bundler version. -* `allow_deployment_source_credential_changes` (`BUNDLE_ALLOW_DEPLOYMENT_SOURCE_CREDENTIAL_CHANGES`): - When in deployment mode, allow changing the credentials to a gem's source. - Ex: `https://some.host.com/gems/path/` -> `https://user_name:password@some.host.com/gems/path` -* `allow_offline_install` (`BUNDLE_ALLOW_OFFLINE_INSTALL`): - Allow Bundler to use cached data when installing without network access. -* `auto_clean_without_path` (`BUNDLE_AUTO_CLEAN_WITHOUT_PATH`): - Automatically run `bundle clean` after installing when an explicit `path` - has not been set and Bundler is not installing into the system gems. -* `auto_install` (`BUNDLE_AUTO_INSTALL`): - Automatically run `bundle install` when gems are missing. -* `bin` (`BUNDLE_BIN`): - Install executables from gems in the bundle to the specified directory. - Defaults to `false`. -* `cache_all` (`BUNDLE_CACHE_ALL`): - Cache all gems, including path and git gems. This needs to be explicitly - configured on bundler 1 and bundler 2, but will be the default on bundler 3. -* `cache_all_platforms` (`BUNDLE_CACHE_ALL_PLATFORMS`): - Cache gems for all platforms. -* `cache_path` (`BUNDLE_CACHE_PATH`): - The directory that bundler will place cached gems in when running - <code>bundle package</code>, and that bundler will look in when installing gems. - Defaults to `vendor/cache`. -* `clean` (`BUNDLE_CLEAN`): - Whether Bundler should run `bundle clean` automatically after - `bundle install`. -* `console` (`BUNDLE_CONSOLE`): - The console that `bundle console` starts. Defaults to `irb`. -* `default_install_uses_path` (`BUNDLE_DEFAULT_INSTALL_USES_PATH`): - Whether a `bundle install` without an explicit `--path` argument defaults - to installing gems in `.bundle`. -* `deployment` (`BUNDLE_DEPLOYMENT`): - Disallow changes to the `Gemfile`. When the `Gemfile` is changed and the - lockfile has not been updated, running Bundler commands will be blocked. -* `disable_checksum_validation` (`BUNDLE_DISABLE_CHECKSUM_VALIDATION`): - Allow installing gems even if they do not match the checksum provided by - RubyGems. -* `disable_exec_load` (`BUNDLE_DISABLE_EXEC_LOAD`): - Stop Bundler from using `load` to launch an executable in-process in - `bundle exec`. -* `disable_local_branch_check` (`BUNDLE_DISABLE_LOCAL_BRANCH_CHECK`): - Allow Bundler to use a local git override without a branch specified in the - Gemfile. -* `disable_multisource` (`BUNDLE_DISABLE_MULTISOURCE`): - When set, Gemfiles containing multiple sources will produce errors - instead of warnings. - Use `bundle config unset disable_multisource` to unset. -* `disable_shared_gems` (`BUNDLE_DISABLE_SHARED_GEMS`): - Stop Bundler from accessing gems installed to RubyGems' normal location. -* `disable_version_check` (`BUNDLE_DISABLE_VERSION_CHECK`): - Stop Bundler from checking if a newer Bundler version is available on - rubygems.org. -* `force_ruby_platform` (`BUNDLE_FORCE_RUBY_PLATFORM`): - Ignore the current machine's platform and install only `ruby` platform gems. - As a result, gems with native extensions will be compiled from source. -* `frozen` (`BUNDLE_FROZEN`): - Disallow changes to the `Gemfile`. When the `Gemfile` is changed and the - lockfile has not been updated, running Bundler commands will be blocked. - Defaults to `true` when `--deployment` is used. -* `gem.push_key` (`BUNDLE_GEM__PUSH_KEY`): - Sets the `--key` parameter for `gem push` when using the `rake release` - command with a private gemstash server. -* `gemfile` (`BUNDLE_GEMFILE`): - The name of the file that bundler should use as the `Gemfile`. This location - of this file also sets the root of the project, which is used to resolve - relative paths in the `Gemfile`, among other things. By default, bundler - will search up from the current working directory until it finds a - `Gemfile`. -* `global_gem_cache` (`BUNDLE_GLOBAL_GEM_CACHE`): - Whether Bundler should cache all gems globally, rather than locally to the - installing Ruby installation. -* `ignore_messages` (`BUNDLE_IGNORE_MESSAGES`): When set, no post install - messages will be printed. To silence a single gem, use dot notation like - `ignore_messages.httparty true`. -* `init_gems_rb` (`BUNDLE_INIT_GEMS_RB`) - Generate a `gems.rb` instead of a `Gemfile` when running `bundle init`. -* `jobs` (`BUNDLE_JOBS`): - The number of gems Bundler can install in parallel. Defaults to 1. -* `no_install` (`BUNDLE_NO_INSTALL`): - Whether `bundle package` should skip installing gems. -* `no_prune` (`BUNDLE_NO_PRUNE`): - Whether Bundler should leave outdated gems unpruned when caching. -* `only_update_to_newer_versions` (`BUNDLE_ONLY_UPDATE_TO_NEWER_VERSIONS`): - During `bundle update`, only resolve to newer versions of the gems in the - lockfile. -* `path` (`BUNDLE_PATH`): - The location on disk where all gems in your bundle will be located regardless - of `$GEM_HOME` or `$GEM_PATH` values. Bundle gems not found in this location - will be installed by `bundle install`. Defaults to `Gem.dir`. When --deployment - is used, defaults to vendor/bundle. -* `path.system` (`BUNDLE_PATH__SYSTEM`): - Whether Bundler will install gems into the default system path (`Gem.dir`). -* `path_relative_to_cwd` (`BUNDLE_PATH_RELATIVE_TO_CWD`) - Makes `--path` relative to the CWD instead of the `Gemfile`. -* `plugins` (`BUNDLE_PLUGINS`): - Enable Bundler's experimental plugin system. -* `prefer_patch` (BUNDLE_PREFER_PATCH): - Prefer updating only to next patch version during updates. Makes `bundle update` calls equivalent to `bundler update --patch`. -* `print_only_version_number` (`BUNDLE_PRINT_ONLY_VERSION_NUMBER`) - Print only version number from `bundler --version`. -* `redirect` (`BUNDLE_REDIRECT`): - The number of redirects allowed for network requests. Defaults to `5`. -* `retry` (`BUNDLE_RETRY`): - The number of times to retry failed network requests. Defaults to `3`. -* `setup_makes_kernel_gem_public` (`BUNDLE_SETUP_MAKES_KERNEL_GEM_PUBLIC`): - Have `Bundler.setup` make the `Kernel#gem` method public, even though - RubyGems declares it as private. -* `shebang` (`BUNDLE_SHEBANG`): - The program name that should be invoked for generated binstubs. Defaults to - the ruby install name used to generate the binstub. -* `silence_deprecations` (`BUNDLE_SILENCE_DEPRECATIONS`): - Whether Bundler should silence deprecation warnings for behavior that will - be changed in the next major version. -* `silence_root_warning` (`BUNDLE_SILENCE_ROOT_WARNING`): - Silence the warning Bundler prints when installing gems as root. -* `specific_platform` (`BUNDLE_SPECIFIC_PLATFORM`): - Allow bundler to resolve for the specific running platform and store it in - the lockfile, instead of only using a generic platform. - A specific platform is the exact platform triple reported by - `Gem::Platform.local`, such as `x86_64-darwin-16` or `universal-java-1.8`. - On the other hand, generic platforms are those such as `ruby`, `mswin`, or - `java`. In this example, `x86_64-darwin-16` would map to `ruby` and - `universal-java-1.8` to `java`. -* `ssl_ca_cert` (`BUNDLE_SSL_CA_CERT`): - Path to a designated CA certificate file or folder containing multiple - certificates for trusted CAs in PEM format. -* `ssl_client_cert` (`BUNDLE_SSL_CLIENT_CERT`): - Path to a designated file containing a X.509 client certificate - and key in PEM format. -* `ssl_verify_mode` (`BUNDLE_SSL_VERIFY_MODE`): - The SSL verification mode Bundler uses when making HTTPS requests. - Defaults to verify peer. -* `suppress_install_using_messages` (`BUNDLE_SUPPRESS_INSTALL_USING_MESSAGES`): - Avoid printing `Using ...` messages during installation when the version of - a gem has not changed. -* `system_bindir` (`BUNDLE_SYSTEM_BINDIR`): - The location where RubyGems installs binstubs. Defaults to `Gem.bindir`. -* `timeout` (`BUNDLE_TIMEOUT`): - The seconds allowed before timing out for network requests. Defaults to `10`. -* `unlock_source_unlocks_spec` (`BUNDLE_UNLOCK_SOURCE_UNLOCKS_SPEC`): - Whether running `bundle update --source NAME` unlocks a gem with the given - name. Defaults to `true`. -* `update_requires_all_flag` (`BUNDLE_UPDATE_REQUIRES_ALL_FLAG`) - Require passing `--all` to `bundle update` when everything should be updated, - and disallow passing no options to `bundle update`. -* `user_agent` (`BUNDLE_USER_AGENT`): - The custom user agent fragment Bundler includes in API requests. -* `with` (`BUNDLE_WITH`): - A `:`-separated list of groups whose gems bundler should install. -* `without` (`BUNDLE_WITHOUT`): - A `:`-separated list of groups whose gems bundler should not install. - -In general, you should set these settings per-application by using the applicable -flag to the [bundle install(1)](bundle-install.1.html) or [bundle package(1)](bundle-package.1.html) command. - -You can set them globally either via environment variables or `bundle config`, -whichever is preferable for your setup. If you use both, environment variables -will take preference over global settings. - -## LOCAL GIT REPOS - -Bundler also allows you to work against a git repository locally -instead of using the remote version. This can be achieved by setting -up a local override: - - bundle config set --local local.GEM_NAME /path/to/local/git/repository - -For example, in order to use a local Rack repository, a developer could call: - - bundle config set --local local.rack ~/Work/git/rack - -Now instead of checking out the remote git repository, the local -override will be used. Similar to a path source, every time the local -git repository change, changes will be automatically picked up by -Bundler. This means a commit in the local git repo will update the -revision in the `Gemfile.lock` to the local git repo revision. This -requires the same attention as git submodules. Before pushing to -the remote, you need to ensure the local override was pushed, otherwise -you may point to a commit that only exists in your local machine. -You'll also need to CGI escape your usernames and passwords as well. - -Bundler does many checks to ensure a developer won't work with -invalid references. Particularly, we force a developer to specify -a branch in the `Gemfile` in order to use this feature. If the branch -specified in the `Gemfile` and the current branch in the local git -repository do not match, Bundler will abort. This ensures that -a developer is always working against the correct branches, and prevents -accidental locking to a different branch. - -Finally, Bundler also ensures that the current revision in the -`Gemfile.lock` exists in the local git repository. By doing this, Bundler -forces you to fetch the latest changes in the remotes. - -## MIRRORS OF GEM SOURCES - -Bundler supports overriding gem sources with mirrors. This allows you to -configure rubygems.org as the gem source in your Gemfile while still using your -mirror to fetch gems. - - bundle config set --global mirror.SOURCE_URL MIRROR_URL - -For example, to use a mirror of rubygems.org hosted at rubygems-mirror.org: - - bundle config set --global mirror.http://rubygems.org http://rubygems-mirror.org - -Each mirror also provides a fallback timeout setting. If the mirror does not -respond within the fallback timeout, Bundler will try to use the original -server instead of the mirror. - - bundle config set --global mirror.SOURCE_URL.fallback_timeout TIMEOUT - -For example, to fall back to rubygems.org after 3 seconds: - - bundle config set --global mirror.https://rubygems.org.fallback_timeout 3 - -The default fallback timeout is 0.1 seconds, but the setting can currently -only accept whole seconds (for example, 1, 15, or 30). - -## CREDENTIALS FOR GEM SOURCES - -Bundler allows you to configure credentials for any gem source, which allows -you to avoid putting secrets into your Gemfile. - - bundle config set --global SOURCE_HOSTNAME USERNAME:PASSWORD - -For example, to save the credentials of user `claudette` for the gem source at -`gems.longerous.com`, you would run: - - bundle config set --global gems.longerous.com claudette:s00pers3krit - -Or you can set the credentials as an environment variable like this: - - export BUNDLE_GEMS__LONGEROUS__COM="claudette:s00pers3krit" - -For gems with a git source with HTTP(S) URL you can specify credentials like so: - - bundle config set --global https://github.com/bundler/bundler.git username:password - -Or you can set the credentials as an environment variable like so: - - export BUNDLE_GITHUB__COM=username:password - -This is especially useful for private repositories on hosts such as Github, -where you can use personal OAuth tokens: - - export BUNDLE_GITHUB__COM=abcd0123generatedtoken:x-oauth-basic - - -## CONFIGURE BUNDLER DIRECTORIES - -Bundler's home, config, cache and plugin directories are able to be configured -through environment variables. The default location for Bundler's home directory is -`~/.bundle`, which all directories inherit from by default. The following -outlines the available environment variables and their default values - - BUNDLE_USER_HOME : $HOME/.bundle - BUNDLE_USER_CACHE : $BUNDLE_USER_HOME/cache - BUNDLE_USER_CONFIG : $BUNDLE_USER_HOME/config - BUNDLE_USER_PLUGIN : $BUNDLE_USER_HOME/plugin diff --git a/man/bundle-doctor.1 b/man/bundle-doctor.1 deleted file mode 100644 index 82f0fc6fba..0000000000 --- a/man/bundle-doctor.1 +++ /dev/null @@ -1,44 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-DOCTOR" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-doctor\fR \- Checks the bundle for common problems -. -.SH "SYNOPSIS" -\fBbundle doctor\fR [\-\-quiet] [\-\-gemfile=GEMFILE] -. -.SH "DESCRIPTION" -Checks your Gemfile and gem environment for common problems\. If issues are detected, Bundler prints them and exits status 1\. Otherwise, Bundler prints a success message and exits status 0\. -. -.P -Examples of common problems caught by bundle\-doctor include: -. -.IP "\(bu" 4 -Invalid Bundler settings -. -.IP "\(bu" 4 -Mismatched Ruby versions -. -.IP "\(bu" 4 -Mismatched platforms -. -.IP "\(bu" 4 -Uninstalled gems -. -.IP "\(bu" 4 -Missing dependencies -. -.IP "" 0 -. -.SH "OPTIONS" -. -.TP -\fB\-\-quiet\fR -Only output warnings and errors\. -. -.TP -\fB\-\-gemfile=<gemfile>\fR -The location of the Gemfile(5) which Bundler should use\. This defaults to a Gemfile(5) in the current working directory\. In general, Bundler will assume that the location of the Gemfile(5) is also the project\'s root and will try to find \fBGemfile\.lock\fR and \fBvendor/cache\fR relative to this location\. - diff --git a/man/bundle-doctor.1.ronn b/man/bundle-doctor.1.ronn deleted file mode 100644 index 271ee800ad..0000000000 --- a/man/bundle-doctor.1.ronn +++ /dev/null @@ -1,33 +0,0 @@ -bundle-doctor(1) -- Checks the bundle for common problems -========================================================= - -## SYNOPSIS - -`bundle doctor` [--quiet] - [--gemfile=GEMFILE] - -## DESCRIPTION - -Checks your Gemfile and gem environment for common problems. If issues -are detected, Bundler prints them and exits status 1. Otherwise, -Bundler prints a success message and exits status 0. - -Examples of common problems caught by bundle-doctor include: - -* Invalid Bundler settings -* Mismatched Ruby versions -* Mismatched platforms -* Uninstalled gems -* Missing dependencies - -## OPTIONS - -* `--quiet`: - Only output warnings and errors. - -* `--gemfile=<gemfile>`: - The location of the Gemfile(5) which Bundler should use. This defaults - to a Gemfile(5) in the current working directory. In general, Bundler - will assume that the location of the Gemfile(5) is also the project's - root and will try to find `Gemfile.lock` and `vendor/cache` relative - to this location. diff --git a/man/bundle-exec.1 b/man/bundle-exec.1 deleted file mode 100644 index 4dc42bed28..0000000000 --- a/man/bundle-exec.1 +++ /dev/null @@ -1,165 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-EXEC" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-exec\fR \- Execute a command in the context of the bundle -. -.SH "SYNOPSIS" -\fBbundle exec\fR [\-\-keep\-file\-descriptors] \fIcommand\fR -. -.SH "DESCRIPTION" -This command executes the command, making all gems specified in the [\fBGemfile(5)\fR][Gemfile(5)] available to \fBrequire\fR in Ruby programs\. -. -.P -Essentially, if you would normally have run something like \fBrspec spec/my_spec\.rb\fR, and you want to use the gems specified in the [\fBGemfile(5)\fR][Gemfile(5)] and installed via bundle install(1) \fIbundle\-install\.1\.html\fR, you should run \fBbundle exec rspec spec/my_spec\.rb\fR\. -. -.P -Note that \fBbundle exec\fR does not require that an executable is available on your shell\'s \fB$PATH\fR\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-keep\-file\-descriptors\fR -Exec in Ruby 2\.0 began discarding non\-standard file descriptors\. When this flag is passed, exec will revert to the 1\.9 behaviour of passing all file descriptors to the new process\. -. -.SH "BUNDLE INSTALL \-\-BINSTUBS" -If you use the \fB\-\-binstubs\fR flag in bundle install(1) \fIbundle\-install\.1\.html\fR, Bundler will automatically create a directory (which defaults to \fBapp_root/bin\fR) containing all of the executables available from gems in the bundle\. -. -.P -After using \fB\-\-binstubs\fR, \fBbin/rspec spec/my_spec\.rb\fR is identical to \fBbundle exec rspec spec/my_spec\.rb\fR\. -. -.SH "ENVIRONMENT MODIFICATIONS" -\fBbundle exec\fR makes a number of changes to the shell environment, then executes the command you specify in full\. -. -.IP "\(bu" 4 -make sure that it\'s still possible to shell out to \fBbundle\fR from inside a command invoked by \fBbundle exec\fR (using \fB$BUNDLE_BIN_PATH\fR) -. -.IP "\(bu" 4 -put the directory containing executables (like \fBrails\fR, \fBrspec\fR, \fBrackup\fR) for your bundle on \fB$PATH\fR -. -.IP "\(bu" 4 -make sure that if bundler is invoked in the subshell, it uses the same \fBGemfile\fR (by setting \fBBUNDLE_GEMFILE\fR) -. -.IP "\(bu" 4 -add \fB\-rbundler/setup\fR to \fB$RUBYOPT\fR, which makes sure that Ruby programs invoked in the subshell can see the gems in the bundle -. -.IP "" 0 -. -.P -It also modifies Rubygems: -. -.IP "\(bu" 4 -disallow loading additional gems not in the bundle -. -.IP "\(bu" 4 -modify the \fBgem\fR method to be a no\-op if a gem matching the requirements is in the bundle, and to raise a \fBGem::LoadError\fR if it\'s not -. -.IP "\(bu" 4 -Define \fBGem\.refresh\fR to be a no\-op, since the source index is always frozen when using bundler, and to prevent gems from the system leaking into the environment -. -.IP "\(bu" 4 -Override \fBGem\.bin_path\fR to use the gems in the bundle, making system executables work -. -.IP "\(bu" 4 -Add all gems in the bundle into Gem\.loaded_specs -. -.IP "" 0 -. -.P -Finally, \fBbundle exec\fR also implicitly modifies \fBGemfile\.lock\fR if the lockfile and the Gemfile do not match\. Bundler needs the Gemfile to determine things such as a gem\'s groups, \fBautorequire\fR, and platforms, etc\., and that information isn\'t stored in the lockfile\. The Gemfile and lockfile must be synced in order to \fBbundle exec\fR successfully, so \fBbundle exec\fR updates the lockfile beforehand\. -. -.SS "Loading" -By default, when attempting to \fBbundle exec\fR to a file with a ruby shebang, Bundler will \fBKernel\.load\fR that file instead of using \fBKernel\.exec\fR\. For the vast majority of cases, this is a performance improvement\. In a rare few cases, this could cause some subtle side\-effects (such as dependence on the exact contents of \fB$0\fR or \fB__FILE__\fR) and the optimization can be disabled by enabling the \fBdisable_exec_load\fR setting\. -. -.SS "Shelling out" -Any Ruby code that opens a subshell (like \fBsystem\fR, backticks, or \fB%x{}\fR) will automatically use the current Bundler environment\. If you need to shell out to a Ruby command that is not part of your current bundle, use the \fBwith_clean_env\fR method with a block\. Any subshells created inside the block will be given the environment present before Bundler was activated\. For example, Homebrew commands run Ruby, but don\'t work inside a bundle: -. -.IP "" 4 -. -.nf - -Bundler\.with_clean_env do - `brew install wget` -end -. -.fi -. -.IP "" 0 -. -.P -Using \fBwith_clean_env\fR is also necessary if you are shelling out to a different bundle\. Any Bundler commands run in a subshell will inherit the current Gemfile, so commands that need to run in the context of a different bundle also need to use \fBwith_clean_env\fR\. -. -.IP "" 4 -. -.nf - -Bundler\.with_clean_env do - Dir\.chdir "/other/bundler/project" do - `bundle exec \./script` - end -end -. -.fi -. -.IP "" 0 -. -.P -Bundler provides convenience helpers that wrap \fBsystem\fR and \fBexec\fR, and they can be used like this: -. -.IP "" 4 -. -.nf - -Bundler\.clean_system(\'brew install wget\') -Bundler\.clean_exec(\'brew install wget\') -. -.fi -. -.IP "" 0 -. -.SH "RUBYGEMS PLUGINS" -At present, the Rubygems plugin system requires all files named \fBrubygems_plugin\.rb\fR on the load path of \fIany\fR installed gem when any Ruby code requires \fBrubygems\.rb\fR\. This includes executables installed into the system, like \fBrails\fR, \fBrackup\fR, and \fBrspec\fR\. -. -.P -Since Rubygems plugins can contain arbitrary Ruby code, they commonly end up activating themselves or their dependencies\. -. -.P -For instance, the \fBgemcutter 0\.5\fR gem depended on \fBjson_pure\fR\. If you had that version of gemcutter installed (even if you \fIalso\fR had a newer version without this problem), Rubygems would activate \fBgemcutter 0\.5\fR and \fBjson_pure <latest>\fR\. -. -.P -If your Gemfile(5) also contained \fBjson_pure\fR (or a gem with a dependency on \fBjson_pure\fR), the latest version on your system might conflict with the version in your Gemfile(5), or the snapshot version in your \fBGemfile\.lock\fR\. -. -.P -If this happens, bundler will say: -. -.IP "" 4 -. -.nf - -You have already activated json_pure 1\.4\.6 but your Gemfile -requires json_pure 1\.4\.3\. Consider using bundle exec\. -. -.fi -. -.IP "" 0 -. -.P -In this situation, you almost certainly want to remove the underlying gem with the problematic gem plugin\. In general, the authors of these plugins (in this case, the \fBgemcutter\fR gem) have released newer versions that are more careful in their plugins\. -. -.P -You can find a list of all the gems containing gem plugins by running -. -.IP "" 4 -. -.nf - -ruby \-rrubygems \-e "puts Gem\.find_files(\'rubygems_plugin\.rb\')" -. -.fi -. -.IP "" 0 -. -.P -At the very least, you should remove all but the newest version of each gem plugin, and also remove all gem plugins that you aren\'t using (\fBgem uninstall gem_name\fR)\. diff --git a/man/bundle-exec.1.ronn b/man/bundle-exec.1.ronn deleted file mode 100644 index dec3c7cb82..0000000000 --- a/man/bundle-exec.1.ronn +++ /dev/null @@ -1,152 +0,0 @@ -bundle-exec(1) -- Execute a command in the context of the bundle -================================================================ - -## SYNOPSIS - -`bundle exec` [--keep-file-descriptors] <command> - -## DESCRIPTION - -This command executes the command, making all gems specified in the -[`Gemfile(5)`][Gemfile(5)] available to `require` in Ruby programs. - -Essentially, if you would normally have run something like -`rspec spec/my_spec.rb`, and you want to use the gems specified -in the [`Gemfile(5)`][Gemfile(5)] and installed via [bundle install(1)](bundle-install.1.html), you -should run `bundle exec rspec spec/my_spec.rb`. - -Note that `bundle exec` does not require that an executable is -available on your shell's `$PATH`. - -## OPTIONS - -* `--keep-file-descriptors`: - Exec in Ruby 2.0 began discarding non-standard file descriptors. When this - flag is passed, exec will revert to the 1.9 behaviour of passing all file - descriptors to the new process. - -## BUNDLE INSTALL --BINSTUBS - -If you use the `--binstubs` flag in [bundle install(1)](bundle-install.1.html), Bundler will -automatically create a directory (which defaults to `app_root/bin`) -containing all of the executables available from gems in the bundle. - -After using `--binstubs`, `bin/rspec spec/my_spec.rb` is identical -to `bundle exec rspec spec/my_spec.rb`. - -## ENVIRONMENT MODIFICATIONS - -`bundle exec` makes a number of changes to the shell environment, -then executes the command you specify in full. - -* make sure that it's still possible to shell out to `bundle` - from inside a command invoked by `bundle exec` (using - `$BUNDLE_BIN_PATH`) -* put the directory containing executables (like `rails`, `rspec`, - `rackup`) for your bundle on `$PATH` -* make sure that if bundler is invoked in the subshell, it uses - the same `Gemfile` (by setting `BUNDLE_GEMFILE`) -* add `-rbundler/setup` to `$RUBYOPT`, which makes sure that - Ruby programs invoked in the subshell can see the gems in - the bundle - -It also modifies Rubygems: - -* disallow loading additional gems not in the bundle -* modify the `gem` method to be a no-op if a gem matching - the requirements is in the bundle, and to raise a - `Gem::LoadError` if it's not -* Define `Gem.refresh` to be a no-op, since the source - index is always frozen when using bundler, and to - prevent gems from the system leaking into the environment -* Override `Gem.bin_path` to use the gems in the bundle, - making system executables work -* Add all gems in the bundle into Gem.loaded_specs - -Finally, `bundle exec` also implicitly modifies `Gemfile.lock` if the lockfile -and the Gemfile do not match. Bundler needs the Gemfile to determine things -such as a gem's groups, `autorequire`, and platforms, etc., and that -information isn't stored in the lockfile. The Gemfile and lockfile must be -synced in order to `bundle exec` successfully, so `bundle exec` -updates the lockfile beforehand. - -### Loading - -By default, when attempting to `bundle exec` to a file with a ruby shebang, -Bundler will `Kernel.load` that file instead of using `Kernel.exec`. For the -vast majority of cases, this is a performance improvement. In a rare few cases, -this could cause some subtle side-effects (such as dependence on the exact -contents of `$0` or `__FILE__`) and the optimization can be disabled by enabling -the `disable_exec_load` setting. - -### Shelling out - -Any Ruby code that opens a subshell (like `system`, backticks, or `%x{}`) will -automatically use the current Bundler environment. If you need to shell out to -a Ruby command that is not part of your current bundle, use the -`with_clean_env` method with a block. Any subshells created inside the block -will be given the environment present before Bundler was activated. For -example, Homebrew commands run Ruby, but don't work inside a bundle: - - Bundler.with_clean_env do - `brew install wget` - end - -Using `with_clean_env` is also necessary if you are shelling out to a different -bundle. Any Bundler commands run in a subshell will inherit the current -Gemfile, so commands that need to run in the context of a different bundle also -need to use `with_clean_env`. - - Bundler.with_clean_env do - Dir.chdir "/other/bundler/project" do - `bundle exec ./script` - end - end - -Bundler provides convenience helpers that wrap `system` and `exec`, and they -can be used like this: - - Bundler.clean_system('brew install wget') - Bundler.clean_exec('brew install wget') - - -## RUBYGEMS PLUGINS - -At present, the Rubygems plugin system requires all files -named `rubygems_plugin.rb` on the load path of _any_ installed -gem when any Ruby code requires `rubygems.rb`. This includes -executables installed into the system, like `rails`, `rackup`, -and `rspec`. - -Since Rubygems plugins can contain arbitrary Ruby code, they -commonly end up activating themselves or their dependencies. - -For instance, the `gemcutter 0.5` gem depended on `json_pure`. -If you had that version of gemcutter installed (even if -you _also_ had a newer version without this problem), Rubygems -would activate `gemcutter 0.5` and `json_pure <latest>`. - -If your Gemfile(5) also contained `json_pure` (or a gem -with a dependency on `json_pure`), the latest version on -your system might conflict with the version in your -Gemfile(5), or the snapshot version in your `Gemfile.lock`. - -If this happens, bundler will say: - - You have already activated json_pure 1.4.6 but your Gemfile - requires json_pure 1.4.3. Consider using bundle exec. - -In this situation, you almost certainly want to remove the -underlying gem with the problematic gem plugin. In general, -the authors of these plugins (in this case, the `gemcutter` -gem) have released newer versions that are more careful in -their plugins. - -You can find a list of all the gems containing gem plugins -by running - - ruby -rrubygems -e "puts Gem.find_files('rubygems_plugin.rb')" - -At the very least, you should remove all but the newest -version of each gem plugin, and also remove all gem plugins -that you aren't using (`gem uninstall gem_name`). diff --git a/man/bundle-gem.1 b/man/bundle-gem.1 deleted file mode 100644 index 124df739cc..0000000000 --- a/man/bundle-gem.1 +++ /dev/null @@ -1,102 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-GEM" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem -. -.SH "SYNOPSIS" -\fBbundle gem\fR \fIGEM_NAME\fR \fIOPTIONS\fR -. -.SH "DESCRIPTION" -Generates a directory named \fBGEM_NAME\fR with a \fBRakefile\fR, \fBGEM_NAME\.gemspec\fR, and other supporting files and directories that can be used to develop a rubygem with that name\. -. -.P -Run \fBrake \-T\fR in the resulting project for a list of Rake tasks that can be used to test and publish the gem to rubygems\.org\. -. -.P -The generated project skeleton can be customized with OPTIONS, as explained below\. Note that these options can also be specified via Bundler\'s global configuration file using the following names: -. -.IP "\(bu" 4 -\fBgem\.coc\fR -. -.IP "\(bu" 4 -\fBgem\.mit\fR -. -.IP "\(bu" 4 -\fBgem\.test\fR -. -.IP "" 0 -. -.SH "OPTIONS" -. -.TP -\fB\-\-exe\fR or \fB\-b\fR or \fB\-\-bin\fR -Specify that Bundler should create a binary executable (as \fBexe/GEM_NAME\fR) in the generated rubygem project\. This binary will also be added to the \fBGEM_NAME\.gemspec\fR manifest\. This behavior is disabled by default\. -. -.TP -\fB\-\-no\-exe\fR -Do not create a binary (overrides \fB\-\-exe\fR specified in the global config)\. -. -.TP -\fB\-\-coc\fR -Add a \fBCODE_OF_CONDUCT\.md\fR file to the root of the generated project\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. -. -.TP -\fB\-\-no\-coc\fR -Do not create a \fBCODE_OF_CONDUCT\.md\fR (overrides \fB\-\-coc\fR specified in the global config)\. -. -.TP -\fB\-\-ext\fR -Add boilerplate for C extension code to the generated project\. This behavior is disabled by default\. -. -.TP -\fB\-\-no\-ext\fR -Do not add C extension code (overrides \fB\-\-ext\fR specified in the global config)\. -. -.TP -\fB\-\-mit\fR -Add an MIT license to a \fBLICENSE\.txt\fR file in the root of the generated project\. Your name from the global git config is used for the copyright statement\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. -. -.TP -\fB\-\-no\-mit\fR -Do not create a \fBLICENSE\.txt\fR (overrides \fB\-\-mit\fR specified in the global config)\. -. -.TP -\fB\-t\fR, \fB\-\-test=minitest\fR, \fB\-\-test=rspec\fR, \fB\-\-test=test\-unit\fR -Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR, \fBrspec\fR and \fBtest\-unit\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. Given no option is specified: -. -.IP -When Bundler is configured to generate tests, this defaults to Bundler\'s global config setting \fBgem\.test\fR\. -. -.IP -When Bundler is configured to not generate tests, an interactive prompt will be displayed and the answer will be used for the current rubygem project\. -. -.IP -When Bundler is unconfigured, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. -. -.TP -\fB\-\-ci\fR, \fB\-\-ci=github\fR, \fB\-\-ci=travis\fR, \fB\-\-ci=gitlab\fR, \fB\-\-ci=circle\fR -Specify the continuous integration service that Bundler should use when generating the project\. Acceptable values are \fBgithub\fR, \fBtravis\fR, \fBgitlab\fR and \fBcircle\fR\. A configuration file will be generated in the project directory\. Given no option is specified: -. -.IP -When Bundler is configured to generate CI files, this defaults to Bundler\'s global config setting \fBgem\.ci\fR\. -. -.IP -When Bundler is configured to not generate CI files, an interactive prompt will be displayed and the answer will be used for the current rubygem project\. -. -.IP -When Bundler is unconfigured, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. -. -.TP -\fB\-e\fR, \fB\-\-edit[=EDITOR]\fR -Open the resulting GEM_NAME\.gemspec in EDITOR, or the default editor if not specified\. The default is \fB$BUNDLER_EDITOR\fR, \fB$VISUAL\fR, or \fB$EDITOR\fR\. -. -.SH "SEE ALSO" -. -.IP "\(bu" 4 -bundle config(1) \fIbundle\-config\.1\.html\fR -. -.IP "" 0 - diff --git a/man/bundle-gem.1.ronn b/man/bundle-gem.1.ronn deleted file mode 100644 index a997cb907a..0000000000 --- a/man/bundle-gem.1.ronn +++ /dev/null @@ -1,101 +0,0 @@ -bundle-gem(1) -- Generate a project skeleton for creating a rubygem -==================================================================== - -## SYNOPSIS - -`bundle gem` <GEM_NAME> [OPTIONS] - -## DESCRIPTION - -Generates a directory named `GEM_NAME` with a `Rakefile`, `GEM_NAME.gemspec`, -and other supporting files and directories that can be used to develop a -rubygem with that name. - -Run `rake -T` in the resulting project for a list of Rake tasks that can be used -to test and publish the gem to rubygems.org. - -The generated project skeleton can be customized with OPTIONS, as explained -below. Note that these options can also be specified via Bundler's global -configuration file using the following names: - -* `gem.coc` -* `gem.mit` -* `gem.test` - -## OPTIONS - -* `--exe` or `-b` or `--bin`: - Specify that Bundler should create a binary executable (as `exe/GEM_NAME`) - in the generated rubygem project. This binary will also be added to the - `GEM_NAME.gemspec` manifest. This behavior is disabled by default. - -* `--no-exe`: - Do not create a binary (overrides `--exe` specified in the global config). - -* `--coc`: - Add a `CODE_OF_CONDUCT.md` file to the root of the generated project. If - this option is unspecified, an interactive prompt will be displayed and the - answer will be saved in Bundler's global config for future `bundle gem` use. - -* `--no-coc`: - Do not create a `CODE_OF_CONDUCT.md` (overrides `--coc` specified in the - global config). - -* `--ext`: - Add boilerplate for C extension code to the generated project. This behavior - is disabled by default. - -* `--no-ext`: - Do not add C extension code (overrides `--ext` specified in the global - config). - -* `--mit`: - Add an MIT license to a `LICENSE.txt` file in the root of the generated - project. Your name from the global git config is used for the copyright - statement. If this option is unspecified, an interactive prompt will be - displayed and the answer will be saved in Bundler's global config for future - `bundle gem` use. - -* `--no-mit`: - Do not create a `LICENSE.txt` (overrides `--mit` specified in the global - config). - -* `-t`, `--test=minitest`, `--test=rspec`, `--test=test-unit`: - Specify the test framework that Bundler should use when generating the - project. Acceptable values are `minitest`, `rspec` and `test-unit`. The - `GEM_NAME.gemspec` will be configured and a skeleton test/spec directory will - be created based on this option. Given no option is specified: - - When Bundler is configured to generate tests, this defaults to Bundler's - global config setting `gem.test`. - - When Bundler is configured to not generate tests, an interactive prompt will - be displayed and the answer will be used for the current rubygem project. - - When Bundler is unconfigured, an interactive prompt will be displayed and - the answer will be saved in Bundler's global config for future `bundle gem` - use. - -* `--ci`, `--ci=github`, `--ci=travis`, `--ci=gitlab`, `--ci=circle`: - Specify the continuous integration service that Bundler should use when - generating the project. Acceptable values are `github`, `travis`, `gitlab` - and `circle`. A configuration file will be generated in the project directory. - Given no option is specified: - - When Bundler is configured to generate CI files, this defaults to Bundler's - global config setting `gem.ci`. - - When Bundler is configured to not generate CI files, an interactive prompt - will be displayed and the answer will be used for the current rubygem project. - - When Bundler is unconfigured, an interactive prompt will be displayed and - the answer will be saved in Bundler's global config for future `bundle gem` - use. - -* `-e`, `--edit[=EDITOR]`: - Open the resulting GEM_NAME.gemspec in EDITOR, or the default editor if not - specified. The default is `$BUNDLER_EDITOR`, `$VISUAL`, or `$EDITOR`. - -## SEE ALSO - -* [bundle config(1)](bundle-config.1.html) diff --git a/man/bundle-info.1 b/man/bundle-info.1 deleted file mode 100644 index 2d860d51ab..0000000000 --- a/man/bundle-info.1 +++ /dev/null @@ -1,20 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-INFO" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-info\fR \- Show information for the given gem in your bundle -. -.SH "SYNOPSIS" -\fBbundle info\fR [GEM] [\-\-path] -. -.SH "DESCRIPTION" -Print the basic information about the provided GEM such as homepage, version, path and summary\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-path\fR -Print the path of the given gem - diff --git a/man/bundle-info.1.ronn b/man/bundle-info.1.ronn deleted file mode 100644 index 47e457aa3c..0000000000 --- a/man/bundle-info.1.ronn +++ /dev/null @@ -1,17 +0,0 @@ -bundle-info(1) -- Show information for the given gem in your bundle -========================================================================= - -## SYNOPSIS - -`bundle info` [GEM] - [--path] - -## DESCRIPTION - -Print the basic information about the provided GEM such as homepage, version, -path and summary. - -## OPTIONS - -* `--path`: -Print the path of the given gem diff --git a/man/bundle-init.1 b/man/bundle-init.1 deleted file mode 100644 index c21e269071..0000000000 --- a/man/bundle-init.1 +++ /dev/null @@ -1,25 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-INIT" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-init\fR \- Generates a Gemfile into the current working directory -. -.SH "SYNOPSIS" -\fBbundle init\fR [\-\-gemspec=FILE] -. -.SH "DESCRIPTION" -Init generates a default [\fBGemfile(5)\fR][Gemfile(5)] in the current working directory\. When adding a [\fBGemfile(5)\fR][Gemfile(5)] to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created [\fBGemfile(5)\fR][Gemfile(5)]\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-gemspec\fR -Use the specified \.gemspec to create the [\fBGemfile(5)\fR][Gemfile(5)] -. -.SH "FILES" -Included in the default [\fBGemfile(5)\fR][Gemfile(5)] generated is the line \fB# frozen_string_literal: true\fR\. This is a magic comment supported for the first time in Ruby 2\.3\. The presence of this line results in all string literals in the file being implicitly frozen\. -. -.SH "SEE ALSO" -Gemfile(5) \fIhttps://bundler\.io/man/gemfile\.5\.html\fR diff --git a/man/bundle-init.1.ronn b/man/bundle-init.1.ronn deleted file mode 100644 index 9d3d97deea..0000000000 --- a/man/bundle-init.1.ronn +++ /dev/null @@ -1,29 +0,0 @@ -bundle-init(1) -- Generates a Gemfile into the current working directory -======================================================================== - -## SYNOPSIS - -`bundle init` [--gemspec=FILE] - -## DESCRIPTION - -Init generates a default [`Gemfile(5)`][Gemfile(5)] in the current working directory. When -adding a [`Gemfile(5)`][Gemfile(5)] to a gem with a gemspec, the `--gemspec` option will -automatically add each dependency listed in the gemspec file to the newly -created [`Gemfile(5)`][Gemfile(5)]. - -## OPTIONS - -* `--gemspec`: - Use the specified .gemspec to create the [`Gemfile(5)`][Gemfile(5)] - -## FILES - -Included in the default [`Gemfile(5)`][Gemfile(5)] -generated is the line `# frozen_string_literal: true`. This is a magic comment -supported for the first time in Ruby 2.3. The presence of this line -results in all string literals in the file being implicitly frozen. - -## SEE ALSO - -[Gemfile(5)](https://bundler.io/man/gemfile.5.html) diff --git a/man/bundle-inject.1 b/man/bundle-inject.1 deleted file mode 100644 index 20bcbba735..0000000000 --- a/man/bundle-inject.1 +++ /dev/null @@ -1,33 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-INJECT" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile -. -.SH "SYNOPSIS" -\fBbundle inject\fR [GEM] [VERSION] -. -.SH "DESCRIPTION" -Adds the named gem(s) with their version requirements to the resolved [\fBGemfile(5)\fR][Gemfile(5)]\. -. -.P -This command will add the gem to both your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock if it isn\'t listed yet\. -. -.P -Example: -. -.IP "" 4 -. -.nf - -bundle install -bundle inject \'rack\' \'> 0\' -. -.fi -. -.IP "" 0 -. -.P -This will inject the \'rack\' gem with a version greater than 0 in your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock diff --git a/man/bundle-inject.1.ronn b/man/bundle-inject.1.ronn deleted file mode 100644 index f454341896..0000000000 --- a/man/bundle-inject.1.ronn +++ /dev/null @@ -1,22 +0,0 @@ -bundle-inject(1) -- Add named gem(s) with version requirements to Gemfile -========================================================================= - -## SYNOPSIS - -`bundle inject` [GEM] [VERSION] - -## DESCRIPTION - -Adds the named gem(s) with their version requirements to the resolved -[`Gemfile(5)`][Gemfile(5)]. - -This command will add the gem to both your [`Gemfile(5)`][Gemfile(5)] and Gemfile.lock if it -isn't listed yet. - -Example: - - bundle install - bundle inject 'rack' '> 0' - -This will inject the 'rack' gem with a version greater than 0 in your -[`Gemfile(5)`][Gemfile(5)] and Gemfile.lock diff --git a/man/bundle-install.1 b/man/bundle-install.1 deleted file mode 100644 index 0abd1a31e2..0000000000 --- a/man/bundle-install.1 +++ /dev/null @@ -1,338 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-INSTALL" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-install\fR \- Install the dependencies specified in your Gemfile -. -.SH "SYNOPSIS" -\fBbundle install\fR [\-\-binstubs[=DIRECTORY]] [\-\-clean] [\-\-deployment] [\-\-frozen] [\-\-full\-index] [\-\-gemfile=GEMFILE] [\-\-jobs=NUMBER] [\-\-local] [\-\-no\-cache] [\-\-no\-prune] [\-\-path PATH] [\-\-quiet] [\-\-redownload] [\-\-retry=NUMBER] [\-\-shebang] [\-\-standalone[=GROUP[ GROUP\.\.\.]]] [\-\-system] [\-\-trust\-policy=POLICY] [\-\-with=GROUP[ GROUP\.\.\.]] [\-\-without=GROUP[ GROUP\.\.\.]] -. -.SH "DESCRIPTION" -Install the gems specified in your Gemfile(5)\. If this is the first time you run bundle install (and a \fBGemfile\.lock\fR does not exist), Bundler will fetch all remote sources, resolve dependencies and install all needed gems\. -. -.P -If a \fBGemfile\.lock\fR does exist, and you have not updated your Gemfile(5), Bundler will fetch all remote sources, but use the dependencies specified in the \fBGemfile\.lock\fR instead of resolving dependencies\. -. -.P -If a \fBGemfile\.lock\fR does exist, and you have updated your Gemfile(5), Bundler will use the dependencies in the \fBGemfile\.lock\fR for all gems that you did not update, but will re\-resolve the dependencies of gems that you did update\. You can find more information about this update process below under \fICONSERVATIVE UPDATING\fR\. -. -.SH "OPTIONS" -The \fB\-\-clean\fR, \fB\-\-deployment\fR, \fB\-\-frozen\fR, \fB\-\-no\-prune\fR, \fB\-\-path\fR, \fB\-\-shebang\fR, \fB\-\-system\fR, \fB\-\-without\fR and \fB\-\-with\fR options are deprecated because they only make sense if they are applied to every subsequent \fBbundle install\fR run automatically and that requires \fBbundler\fR to silently remember them\. Since \fBbundler\fR will no longer remember CLI flags in future versions, \fBbundle config\fR (see bundle\-config(1)) should be used to apply them permanently\. -. -.TP -\fB\-\-binstubs[=<directory>]\fR -Binstubs are scripts that wrap around executables\. Bundler creates a small Ruby file (a binstub) that loads Bundler, runs the command, and puts it in \fBbin/\fR\. This lets you link the binstub inside of an application to the exact gem version the application needs\. -. -.IP -Creates a directory (defaults to \fB~/bin\fR) and places any executables from the gem there\. These executables run in Bundler\'s context\. If used, you might add this directory to your environment\'s \fBPATH\fR variable\. For instance, if the \fBrails\fR gem comes with a \fBrails\fR executable, this flag will create a \fBbin/rails\fR executable that ensures that all referred dependencies will be resolved using the bundled gems\. -. -.TP -\fB\-\-clean\fR -On finishing the installation Bundler is going to remove any gems not present in the current Gemfile(5)\. Don\'t worry, gems currently in use will not be removed\. -. -.IP -This option is deprecated in favor of the \fBclean\fR setting\. -. -.TP -\fB\-\-deployment\fR -In \fIdeployment mode\fR, Bundler will \'roll\-out\' the bundle for production or CI use\. Please check carefully if you want to have this option enabled in your development environment\. -. -.IP -This option is deprecated in favor of the \fBdeployment\fR setting\. -. -.TP -\fB\-\-redownload\fR -Force download every gem, even if the required versions are already available locally\. -. -.TP -\fB\-\-frozen\fR -Do not allow the Gemfile\.lock to be updated after this install\. Exits non\-zero if there are going to be changes to the Gemfile\.lock\. -. -.IP -This option is deprecated in favor of the \fBfrozen\fR setting\. -. -.TP -\fB\-\-full\-index\fR -Bundler will not call Rubygems\' API endpoint (default) but download and cache a (currently big) index file of all gems\. Performance can be improved for large bundles that seldom change by enabling this option\. -. -.TP -\fB\-\-gemfile=<gemfile>\fR -The location of the Gemfile(5) which Bundler should use\. This defaults to a Gemfile(5) in the current working directory\. In general, Bundler will assume that the location of the Gemfile(5) is also the project\'s root and will try to find \fBGemfile\.lock\fR and \fBvendor/cache\fR relative to this location\. -. -.TP -\fB\-\-jobs=[<number>]\fR, \fB\-j[<number>]\fR -The maximum number of parallel download and install jobs\. The default is \fB1\fR\. -. -.TP -\fB\-\-local\fR -Do not attempt to connect to \fBrubygems\.org\fR\. Instead, Bundler will use the gems already present in Rubygems\' cache or in \fBvendor/cache\fR\. Note that if a appropriate platform\-specific gem exists on \fBrubygems\.org\fR it will not be found\. -. -.TP -\fB\-\-no\-cache\fR -Do not update the cache in \fBvendor/cache\fR with the newly bundled gems\. This does not remove any gems in the cache but keeps the newly bundled gems from being cached during the install\. -. -.TP -\fB\-\-no\-prune\fR -Don\'t remove stale gems from the cache when the installation finishes\. -. -.IP -This option is deprecated in favor of the \fBno_prune\fR setting\. -. -.TP -\fB\-\-path=<path>\fR -The location to install the specified gems to\. This defaults to Rubygems\' setting\. Bundler shares this location with Rubygems, \fBgem install \.\.\.\fR will have gem installed there, too\. Therefore, gems installed without a \fB\-\-path \.\.\.\fR setting will show up by calling \fBgem list\fR\. Accordingly, gems installed to other locations will not get listed\. -. -.IP -This option is deprecated in favor of the \fBpath\fR setting\. -. -.TP -\fB\-\-quiet\fR -Do not print progress information to the standard output\. Instead, Bundler will exit using a status code (\fB$?\fR)\. -. -.TP -\fB\-\-retry=[<number>]\fR -Retry failed network or git requests for \fInumber\fR times\. -. -.TP -\fB\-\-shebang=<ruby\-executable>\fR -Uses the specified ruby executable (usually \fBruby\fR) to execute the scripts created with \fB\-\-binstubs\fR\. In addition, if you use \fB\-\-binstubs\fR together with \fB\-\-shebang jruby\fR these executables will be changed to execute \fBjruby\fR instead\. -. -.IP -This option is deprecated in favor of the \fBshebang\fR setting\. -. -.TP -\fB\-\-standalone[=<list>]\fR -Makes a bundle that can work without depending on Rubygems or Bundler at runtime\. A space separated list of groups to install has to be specified\. Bundler creates a directory named \fBbundle\fR and installs the bundle there\. It also generates a \fBbundle/bundler/setup\.rb\fR file to replace Bundler\'s own setup in the manner required\. Using this option implicitly sets \fBpath\fR, which is a [remembered option][REMEMBERED OPTIONS]\. -. -.TP -\fB\-\-system\fR -Installs the gems specified in the bundle to the system\'s Rubygems location\. This overrides any previous configuration of \fB\-\-path\fR\. -. -.IP -This option is deprecated in favor of the \fBsystem\fR setting\. -. -.TP -\fB\-\-trust\-policy=[<policy>]\fR -Apply the Rubygems security policy \fIpolicy\fR, where policy is one of \fBHighSecurity\fR, \fBMediumSecurity\fR, \fBLowSecurity\fR, \fBAlmostNoSecurity\fR, or \fBNoSecurity\fR\. For more details, please see the Rubygems signing documentation linked below in \fISEE ALSO\fR\. -. -.TP -\fB\-\-with=<list>\fR -A space\-separated list of groups referencing gems to install\. If an optional group is given it is installed\. If a group is given that is in the remembered list of groups given to \-\-without, it is removed from that list\. -. -.IP -This option is deprecated in favor of the \fBwith\fR setting\. -. -.TP -\fB\-\-without=<list>\fR -A space\-separated list of groups referencing gems to skip during installation\. If a group is given that is in the remembered list of groups given to \-\-with, it is removed from that list\. -. -.IP -This option is deprecated in favor of the \fBwithout\fR setting\. -. -.SH "DEPLOYMENT MODE" -Bundler\'s defaults are optimized for development\. To switch to defaults optimized for deployment and for CI, use the \fB\-\-deployment\fR flag\. Do not activate deployment mode on development machines, as it will cause an error when the Gemfile(5) is modified\. -. -.IP "1." 4 -A \fBGemfile\.lock\fR is required\. -. -.IP -To ensure that the same versions of the gems you developed with and tested with are also used in deployments, a \fBGemfile\.lock\fR is required\. -. -.IP -This is mainly to ensure that you remember to check your \fBGemfile\.lock\fR into version control\. -. -.IP "2." 4 -The \fBGemfile\.lock\fR must be up to date -. -.IP -In development, you can modify your Gemfile(5) and re\-run \fBbundle install\fR to \fIconservatively update\fR your \fBGemfile\.lock\fR snapshot\. -. -.IP -In deployment, your \fBGemfile\.lock\fR should be up\-to\-date with changes made in your Gemfile(5)\. -. -.IP "3." 4 -Gems are installed to \fBvendor/bundle\fR not your default system location -. -.IP -In development, it\'s convenient to share the gems used in your application with other applications and other scripts that run on the system\. -. -.IP -In deployment, isolation is a more important default\. In addition, the user deploying the application may not have permission to install gems to the system, or the web server may not have permission to read them\. -. -.IP -As a result, \fBbundle install \-\-deployment\fR installs gems to the \fBvendor/bundle\fR directory in the application\. This may be overridden using the \fB\-\-path\fR option\. -. -.IP "" 0 -. -.SH "SUDO USAGE" -By default, Bundler installs gems to the same location as \fBgem install\fR\. -. -.P -In some cases, that location may not be writable by your Unix user\. In that case, Bundler will stage everything in a temporary directory, then ask you for your \fBsudo\fR password in order to copy the gems into their system location\. -. -.P -From your perspective, this is identical to installing the gems directly into the system\. -. -.P -You should never use \fBsudo bundle install\fR\. This is because several other steps in \fBbundle install\fR must be performed as the current user: -. -.IP "\(bu" 4 -Updating your \fBGemfile\.lock\fR -. -.IP "\(bu" 4 -Updating your \fBvendor/cache\fR, if necessary -. -.IP "\(bu" 4 -Checking out private git repositories using your user\'s SSH keys -. -.IP "" 0 -. -.P -Of these three, the first two could theoretically be performed by \fBchown\fRing the resulting files to \fB$SUDO_USER\fR\. The third, however, can only be performed by invoking the \fBgit\fR command as the current user\. Therefore, git gems are downloaded and installed into \fB~/\.bundle\fR rather than $GEM_HOME or $BUNDLE_PATH\. -. -.P -As a result, you should run \fBbundle install\fR as the current user, and Bundler will ask for your password if it is needed to put the gems into their final location\. -. -.SH "INSTALLING GROUPS" -By default, \fBbundle install\fR will install all gems in all groups in your Gemfile(5), except those declared for a different platform\. -. -.P -However, you can explicitly tell Bundler to skip installing certain groups with the \fB\-\-without\fR option\. This option takes a space\-separated list of groups\. -. -.P -While the \fB\-\-without\fR option will skip \fIinstalling\fR the gems in the specified groups, it will still \fIdownload\fR those gems and use them to resolve the dependencies of every gem in your Gemfile(5)\. -. -.P -This is so that installing a different set of groups on another machine (such as a production server) will not change the gems and versions that you have already developed and tested against\. -. -.P -\fBBundler offers a rock\-solid guarantee that the third\-party code you are running in development and testing is also the third\-party code you are running in production\. You can choose to exclude some of that code in different environments, but you will never be caught flat\-footed by different versions of third\-party code being used in different environments\.\fR -. -.P -For a simple illustration, consider the following Gemfile(5): -. -.IP "" 4 -. -.nf - -source \'https://rubygems\.org\' - -gem \'sinatra\' - -group :production do - gem \'rack\-perftools\-profiler\' -end -. -.fi -. -.IP "" 0 -. -.P -In this case, \fBsinatra\fR depends on any version of Rack (\fB>= 1\.0\fR), while \fBrack\-perftools\-profiler\fR depends on 1\.x (\fB~> 1\.0\fR)\. -. -.P -When you run \fBbundle install \-\-without production\fR in development, we look at the dependencies of \fBrack\-perftools\-profiler\fR as well\. That way, you do not spend all your time developing against Rack 2\.0, using new APIs unavailable in Rack 1\.x, only to have Bundler switch to Rack 1\.2 when the \fBproduction\fR group \fIis\fR used\. -. -.P -This should not cause any problems in practice, because we do not attempt to \fBinstall\fR the gems in the excluded groups, and only evaluate as part of the dependency resolution process\. -. -.P -This also means that you cannot include different versions of the same gem in different groups, because doing so would result in different sets of dependencies used in development and production\. Because of the vagaries of the dependency resolution process, this usually affects more than the gems you list in your Gemfile(5), and can (surprisingly) radically change the gems you are using\. -. -.SH "THE GEMFILE\.LOCK" -When you run \fBbundle install\fR, Bundler will persist the full names and versions of all gems that you used (including dependencies of the gems specified in the Gemfile(5)) into a file called \fBGemfile\.lock\fR\. -. -.P -Bundler uses this file in all subsequent calls to \fBbundle install\fR, which guarantees that you always use the same exact code, even as your application moves across machines\. -. -.P -Because of the way dependency resolution works, even a seemingly small change (for instance, an update to a point\-release of a dependency of a gem in your Gemfile(5)) can result in radically different gems being needed to satisfy all dependencies\. -. -.P -As a result, you \fBSHOULD\fR check your \fBGemfile\.lock\fR into version control, in both applications and gems\. If you do not, every machine that checks out your repository (including your production server) will resolve all dependencies again, which will result in different versions of third\-party code being used if \fBany\fR of the gems in the Gemfile(5) or any of their dependencies have been updated\. -. -.P -When Bundler first shipped, the \fBGemfile\.lock\fR was included in the \fB\.gitignore\fR file included with generated gems\. Over time, however, it became clear that this practice forces the pain of broken dependencies onto new contributors, while leaving existing contributors potentially unaware of the problem\. Since \fBbundle install\fR is usually the first step towards a contribution, the pain of broken dependencies would discourage new contributors from contributing\. As a result, we have revised our guidance for gem authors to now recommend checking in the lock for gems\. -. -.SH "CONSERVATIVE UPDATING" -When you make a change to the Gemfile(5) and then run \fBbundle install\fR, Bundler will update only the gems that you modified\. -. -.P -In other words, if a gem that you \fBdid not modify\fR worked before you called \fBbundle install\fR, it will continue to use the exact same versions of all dependencies as it used before the update\. -. -.P -Let\'s take a look at an example\. Here\'s your original Gemfile(5): -. -.IP "" 4 -. -.nf - -source \'https://rubygems\.org\' - -gem \'actionpack\', \'2\.3\.8\' -gem \'activemerchant\' -. -.fi -. -.IP "" 0 -. -.P -In this case, both \fBactionpack\fR and \fBactivemerchant\fR depend on \fBactivesupport\fR\. The \fBactionpack\fR gem depends on \fBactivesupport 2\.3\.8\fR and \fBrack ~> 1\.1\.0\fR, while the \fBactivemerchant\fR gem depends on \fBactivesupport >= 2\.3\.2\fR, \fBbraintree >= 2\.0\.0\fR, and \fBbuilder >= 2\.0\.0\fR\. -. -.P -When the dependencies are first resolved, Bundler will select \fBactivesupport 2\.3\.8\fR, which satisfies the requirements of both gems in your Gemfile(5)\. -. -.P -Next, you modify your Gemfile(5) to: -. -.IP "" 4 -. -.nf - -source \'https://rubygems\.org\' - -gem \'actionpack\', \'3\.0\.0\.rc\' -gem \'activemerchant\' -. -.fi -. -.IP "" 0 -. -.P -The \fBactionpack 3\.0\.0\.rc\fR gem has a number of new dependencies, and updates the \fBactivesupport\fR dependency to \fB= 3\.0\.0\.rc\fR and the \fBrack\fR dependency to \fB~> 1\.2\.1\fR\. -. -.P -When you run \fBbundle install\fR, Bundler notices that you changed the \fBactionpack\fR gem, but not the \fBactivemerchant\fR gem\. It evaluates the gems currently being used to satisfy its requirements: -. -.TP -\fBactivesupport 2\.3\.8\fR -also used to satisfy a dependency in \fBactivemerchant\fR, which is not being updated -. -.TP -\fBrack ~> 1\.1\.0\fR -not currently being used to satisfy another dependency -. -.P -Because you did not explicitly ask to update \fBactivemerchant\fR, you would not expect it to suddenly stop working after updating \fBactionpack\fR\. However, satisfying the new \fBactivesupport 3\.0\.0\.rc\fR dependency of actionpack requires updating one of its dependencies\. -. -.P -Even though \fBactivemerchant\fR declares a very loose dependency that theoretically matches \fBactivesupport 3\.0\.0\.rc\fR, Bundler treats gems in your Gemfile(5) that have not changed as an atomic unit together with their dependencies\. In this case, the \fBactivemerchant\fR dependency is treated as \fBactivemerchant 1\.7\.1 + activesupport 2\.3\.8\fR, so \fBbundle install\fR will report that it cannot update \fBactionpack\fR\. -. -.P -To explicitly update \fBactionpack\fR, including its dependencies which other gems in the Gemfile(5) still depend on, run \fBbundle update actionpack\fR (see \fBbundle update(1)\fR)\. -. -.P -\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, which will guarantee that no other gem in the Gemfile(5) is impacted by the change\. If that does not work, run bundle update(1) \fIbundle\-update\.1\.html\fR\. -. -.SH "SEE ALSO" -. -.IP "\(bu" 4 -Gem install docs \fIhttp://guides\.rubygems\.org/rubygems\-basics/#installing\-gems\fR -. -.IP "\(bu" 4 -Rubygems signing docs \fIhttp://guides\.rubygems\.org/security/\fR -. -.IP "" 0 - diff --git a/man/bundle-install.1.ronn b/man/bundle-install.1.ronn deleted file mode 100644 index 07aeb1da90..0000000000 --- a/man/bundle-install.1.ronn +++ /dev/null @@ -1,405 +0,0 @@ -bundle-install(1) -- Install the dependencies specified in your Gemfile -======================================================================= - -## SYNOPSIS - -`bundle install` [--binstubs[=DIRECTORY]] - [--clean] - [--deployment] - [--frozen] - [--full-index] - [--gemfile=GEMFILE] - [--jobs=NUMBER] - [--local] - [--no-cache] - [--no-prune] - [--path PATH] - [--quiet] - [--redownload] - [--retry=NUMBER] - [--shebang] - [--standalone[=GROUP[ GROUP...]]] - [--system] - [--trust-policy=POLICY] - [--with=GROUP[ GROUP...]] - [--without=GROUP[ GROUP...]] - -## DESCRIPTION - -Install the gems specified in your Gemfile(5). If this is the first -time you run bundle install (and a `Gemfile.lock` does not exist), -Bundler will fetch all remote sources, resolve dependencies and -install all needed gems. - -If a `Gemfile.lock` does exist, and you have not updated your Gemfile(5), -Bundler will fetch all remote sources, but use the dependencies -specified in the `Gemfile.lock` instead of resolving dependencies. - -If a `Gemfile.lock` does exist, and you have updated your Gemfile(5), -Bundler will use the dependencies in the `Gemfile.lock` for all gems -that you did not update, but will re-resolve the dependencies of -gems that you did update. You can find more information about this -update process below under [CONSERVATIVE UPDATING][]. - -## OPTIONS - -The `--clean`, `--deployment`, `--frozen`, `--no-prune`, `--path`, `--shebang`, -`--system`, `--without` and `--with` options are deprecated because they only -make sense if they are applied to every subsequent `bundle install` run -automatically and that requires `bundler` to silently remember them. Since -`bundler` will no longer remember CLI flags in future versions, `bundle config` -(see bundle-config(1)) should be used to apply them permanently. - -* `--binstubs[=<directory>]`: - Binstubs are scripts that wrap around executables. Bundler creates a small Ruby - file (a binstub) that loads Bundler, runs the command, and puts it in `bin/`. - This lets you link the binstub inside of an application to the exact gem - version the application needs. - - Creates a directory (defaults to `~/bin`) and places any executables from the - gem there. These executables run in Bundler's context. If used, you might add - this directory to your environment's `PATH` variable. For instance, if the - `rails` gem comes with a `rails` executable, this flag will create a - `bin/rails` executable that ensures that all referred dependencies will be - resolved using the bundled gems. - -* `--clean`: - On finishing the installation Bundler is going to remove any gems not present - in the current Gemfile(5). Don't worry, gems currently in use will not be - removed. - - This option is deprecated in favor of the `clean` setting. - -* `--deployment`: - In [deployment mode][DEPLOYMENT MODE], Bundler will 'roll-out' the bundle for - production or CI use. Please check carefully if you want to have this option - enabled in your development environment. - - This option is deprecated in favor of the `deployment` setting. - -* `--redownload`: - Force download every gem, even if the required versions are already available - locally. - -* `--frozen`: - Do not allow the Gemfile.lock to be updated after this install. Exits - non-zero if there are going to be changes to the Gemfile.lock. - - This option is deprecated in favor of the `frozen` setting. - -* `--full-index`: - Bundler will not call Rubygems' API endpoint (default) but download and cache - a (currently big) index file of all gems. Performance can be improved for - large bundles that seldom change by enabling this option. - -* `--gemfile=<gemfile>`: - The location of the Gemfile(5) which Bundler should use. This defaults - to a Gemfile(5) in the current working directory. In general, Bundler - will assume that the location of the Gemfile(5) is also the project's - root and will try to find `Gemfile.lock` and `vendor/cache` relative - to this location. - -* `--jobs=[<number>]`, `-j[<number>]`: - The maximum number of parallel download and install jobs. The default - is `1`. - -* `--local`: - Do not attempt to connect to `rubygems.org`. Instead, Bundler will use the - gems already present in Rubygems' cache or in `vendor/cache`. Note that if a - appropriate platform-specific gem exists on `rubygems.org` it will not be - found. - -* `--no-cache`: - Do not update the cache in `vendor/cache` with the newly bundled gems. This - does not remove any gems in the cache but keeps the newly bundled gems from - being cached during the install. - -* `--no-prune`: - Don't remove stale gems from the cache when the installation finishes. - - This option is deprecated in favor of the `no_prune` setting. - -* `--path=<path>`: - The location to install the specified gems to. This defaults to Rubygems' - setting. Bundler shares this location with Rubygems, `gem install ...` will - have gem installed there, too. Therefore, gems installed without a - `--path ...` setting will show up by calling `gem list`. Accordingly, gems - installed to other locations will not get listed. - - This option is deprecated in favor of the `path` setting. - -* `--quiet`: - Do not print progress information to the standard output. Instead, Bundler - will exit using a status code (`$?`). - -* `--retry=[<number>]`: - Retry failed network or git requests for <number> times. - -* `--shebang=<ruby-executable>`: - Uses the specified ruby executable (usually `ruby`) to execute the scripts - created with `--binstubs`. In addition, if you use `--binstubs` together with - `--shebang jruby` these executables will be changed to execute `jruby` - instead. - - This option is deprecated in favor of the `shebang` setting. - -* `--standalone[=<list>]`: - Makes a bundle that can work without depending on Rubygems or Bundler at - runtime. A space separated list of groups to install has to be specified. - Bundler creates a directory named `bundle` and installs the bundle there. It - also generates a `bundle/bundler/setup.rb` file to replace Bundler's own setup - in the manner required. Using this option implicitly sets `path`, which is a - [remembered option][REMEMBERED OPTIONS]. - -* `--system`: - Installs the gems specified in the bundle to the system's Rubygems location. - This overrides any previous configuration of `--path`. - - This option is deprecated in favor of the `system` setting. - -* `--trust-policy=[<policy>]`: - Apply the Rubygems security policy <policy>, where policy is one of - `HighSecurity`, `MediumSecurity`, `LowSecurity`, `AlmostNoSecurity`, or - `NoSecurity`. For more details, please see the Rubygems signing documentation - linked below in [SEE ALSO][]. - -* `--with=<list>`: - A space-separated list of groups referencing gems to install. If an - optional group is given it is installed. If a group is given that is - in the remembered list of groups given to --without, it is removed - from that list. - - This option is deprecated in favor of the `with` setting. - -* `--without=<list>`: - A space-separated list of groups referencing gems to skip during installation. - If a group is given that is in the remembered list of groups given - to --with, it is removed from that list. - - This option is deprecated in favor of the `without` setting. - -## DEPLOYMENT MODE - -Bundler's defaults are optimized for development. To switch to -defaults optimized for deployment and for CI, use the `--deployment` -flag. Do not activate deployment mode on development machines, as it -will cause an error when the Gemfile(5) is modified. - -1. A `Gemfile.lock` is required. - - To ensure that the same versions of the gems you developed with - and tested with are also used in deployments, a `Gemfile.lock` - is required. - - This is mainly to ensure that you remember to check your - `Gemfile.lock` into version control. - -2. The `Gemfile.lock` must be up to date - - In development, you can modify your Gemfile(5) and re-run - `bundle install` to [conservatively update][CONSERVATIVE UPDATING] - your `Gemfile.lock` snapshot. - - In deployment, your `Gemfile.lock` should be up-to-date with - changes made in your Gemfile(5). - -3. Gems are installed to `vendor/bundle` not your default system location - - In development, it's convenient to share the gems used in your - application with other applications and other scripts that run on - the system. - - In deployment, isolation is a more important default. In addition, - the user deploying the application may not have permission to install - gems to the system, or the web server may not have permission to - read them. - - As a result, `bundle install --deployment` installs gems to - the `vendor/bundle` directory in the application. This may be - overridden using the `--path` option. - -## SUDO USAGE - -By default, Bundler installs gems to the same location as `gem install`. - -In some cases, that location may not be writable by your Unix user. In -that case, Bundler will stage everything in a temporary directory, -then ask you for your `sudo` password in order to copy the gems into -their system location. - -From your perspective, this is identical to installing the gems -directly into the system. - -You should never use `sudo bundle install`. This is because several -other steps in `bundle install` must be performed as the current user: - -* Updating your `Gemfile.lock` -* Updating your `vendor/cache`, if necessary -* Checking out private git repositories using your user's SSH keys - -Of these three, the first two could theoretically be performed by -`chown`ing the resulting files to `$SUDO_USER`. The third, however, -can only be performed by invoking the `git` command as -the current user. Therefore, git gems are downloaded and installed -into `~/.bundle` rather than $GEM_HOME or $BUNDLE_PATH. - -As a result, you should run `bundle install` as the current user, -and Bundler will ask for your password if it is needed to put the -gems into their final location. - -## INSTALLING GROUPS - -By default, `bundle install` will install all gems in all groups -in your Gemfile(5), except those declared for a different platform. - -However, you can explicitly tell Bundler to skip installing -certain groups with the `--without` option. This option takes -a space-separated list of groups. - -While the `--without` option will skip _installing_ the gems in the -specified groups, it will still _download_ those gems and use them to -resolve the dependencies of every gem in your Gemfile(5). - -This is so that installing a different set of groups on another - machine (such as a production server) will not change the -gems and versions that you have already developed and tested against. - -`Bundler offers a rock-solid guarantee that the third-party -code you are running in development and testing is also the -third-party code you are running in production. You can choose -to exclude some of that code in different environments, but you -will never be caught flat-footed by different versions of -third-party code being used in different environments.` - -For a simple illustration, consider the following Gemfile(5): - - source 'https://rubygems.org' - - gem 'sinatra' - - group :production do - gem 'rack-perftools-profiler' - end - -In this case, `sinatra` depends on any version of Rack (`>= 1.0`), while -`rack-perftools-profiler` depends on 1.x (`~> 1.0`). - -When you run `bundle install --without production` in development, we -look at the dependencies of `rack-perftools-profiler` as well. That way, -you do not spend all your time developing against Rack 2.0, using new -APIs unavailable in Rack 1.x, only to have Bundler switch to Rack 1.2 -when the `production` group _is_ used. - -This should not cause any problems in practice, because we do not -attempt to `install` the gems in the excluded groups, and only evaluate -as part of the dependency resolution process. - -This also means that you cannot include different versions of the same -gem in different groups, because doing so would result in different -sets of dependencies used in development and production. Because of -the vagaries of the dependency resolution process, this usually -affects more than the gems you list in your Gemfile(5), and can -(surprisingly) radically change the gems you are using. - -## THE GEMFILE.LOCK - -When you run `bundle install`, Bundler will persist the full names -and versions of all gems that you used (including dependencies of -the gems specified in the Gemfile(5)) into a file called `Gemfile.lock`. - -Bundler uses this file in all subsequent calls to `bundle install`, -which guarantees that you always use the same exact code, even -as your application moves across machines. - -Because of the way dependency resolution works, even a -seemingly small change (for instance, an update to a point-release -of a dependency of a gem in your Gemfile(5)) can result in radically -different gems being needed to satisfy all dependencies. - -As a result, you `SHOULD` check your `Gemfile.lock` into version -control, in both applications and gems. If you do not, every machine that -checks out your repository (including your production server) will resolve all -dependencies again, which will result in different versions of -third-party code being used if `any` of the gems in the Gemfile(5) -or any of their dependencies have been updated. - -When Bundler first shipped, the `Gemfile.lock` was included in the `.gitignore` -file included with generated gems. Over time, however, it became clear that -this practice forces the pain of broken dependencies onto new contributors, -while leaving existing contributors potentially unaware of the problem. Since -`bundle install` is usually the first step towards a contribution, the pain of -broken dependencies would discourage new contributors from contributing. As a -result, we have revised our guidance for gem authors to now recommend checking -in the lock for gems. - -## CONSERVATIVE UPDATING - -When you make a change to the Gemfile(5) and then run `bundle install`, -Bundler will update only the gems that you modified. - -In other words, if a gem that you `did not modify` worked before -you called `bundle install`, it will continue to use the exact -same versions of all dependencies as it used before the update. - -Let's take a look at an example. Here's your original Gemfile(5): - - source 'https://rubygems.org' - - gem 'actionpack', '2.3.8' - gem 'activemerchant' - -In this case, both `actionpack` and `activemerchant` depend on -`activesupport`. The `actionpack` gem depends on `activesupport 2.3.8` -and `rack ~> 1.1.0`, while the `activemerchant` gem depends on -`activesupport >= 2.3.2`, `braintree >= 2.0.0`, and `builder >= 2.0.0`. - -When the dependencies are first resolved, Bundler will select -`activesupport 2.3.8`, which satisfies the requirements of both -gems in your Gemfile(5). - -Next, you modify your Gemfile(5) to: - - source 'https://rubygems.org' - - gem 'actionpack', '3.0.0.rc' - gem 'activemerchant' - -The `actionpack 3.0.0.rc` gem has a number of new dependencies, -and updates the `activesupport` dependency to `= 3.0.0.rc` and -the `rack` dependency to `~> 1.2.1`. - -When you run `bundle install`, Bundler notices that you changed -the `actionpack` gem, but not the `activemerchant` gem. It -evaluates the gems currently being used to satisfy its requirements: - - * `activesupport 2.3.8`: - also used to satisfy a dependency in `activemerchant`, - which is not being updated - * `rack ~> 1.1.0`: - not currently being used to satisfy another dependency - -Because you did not explicitly ask to update `activemerchant`, -you would not expect it to suddenly stop working after updating -`actionpack`. However, satisfying the new `activesupport 3.0.0.rc` -dependency of actionpack requires updating one of its dependencies. - -Even though `activemerchant` declares a very loose dependency -that theoretically matches `activesupport 3.0.0.rc`, Bundler treats -gems in your Gemfile(5) that have not changed as an atomic unit -together with their dependencies. In this case, the `activemerchant` -dependency is treated as `activemerchant 1.7.1 + activesupport 2.3.8`, -so `bundle install` will report that it cannot update `actionpack`. - -To explicitly update `actionpack`, including its dependencies -which other gems in the Gemfile(5) still depend on, run -`bundle update actionpack` (see `bundle update(1)`). - -`Summary`: In general, after making a change to the Gemfile(5) , you -should first try to run `bundle install`, which will guarantee that no -other gem in the Gemfile(5) is impacted by the change. If that -does not work, run [bundle update(1)](bundle-update.1.html). - -## SEE ALSO - -* [Gem install docs](http://guides.rubygems.org/rubygems-basics/#installing-gems) -* [Rubygems signing docs](http://guides.rubygems.org/security/) diff --git a/man/bundle-list.1 b/man/bundle-list.1 deleted file mode 100644 index ebedb62b38..0000000000 --- a/man/bundle-list.1 +++ /dev/null @@ -1,50 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-LIST" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-list\fR \- List all the gems in the bundle -. -.SH "SYNOPSIS" -\fBbundle list\fR [\-\-name\-only] [\-\-paths] [\-\-without\-group=GROUP[ GROUP\.\.\.]] [\-\-only\-group=GROUP[ GROUP\.\.\.]] -. -.SH "DESCRIPTION" -Prints a list of all the gems in the bundle including their version\. -. -.P -Example: -. -.P -bundle list \-\-name\-only -. -.P -bundle list \-\-paths -. -.P -bundle list \-\-without\-group test -. -.P -bundle list \-\-only\-group dev -. -.P -bundle list \-\-only\-group dev test \-\-paths -. -.SH "OPTIONS" -. -.TP -\fB\-\-name\-only\fR -Print only the name of each gem\. -. -.TP -\fB\-\-paths\fR -Print the path to each gem in the bundle\. -. -.TP -\fB\-\-without\-group=<list>\fR -A space\-separated list of groups of gems to skip during printing\. -. -.TP -\fB\-\-only\-group=<list>\fR -A space\-separated list of groups of gems to print\. - diff --git a/man/bundle-list.1.ronn b/man/bundle-list.1.ronn deleted file mode 100644 index dc058ecd5f..0000000000 --- a/man/bundle-list.1.ronn +++ /dev/null @@ -1,33 +0,0 @@ -bundle-list(1) -- List all the gems in the bundle -========================================================================= - -## SYNOPSIS - -`bundle list` [--name-only] [--paths] [--without-group=GROUP[ GROUP...]] [--only-group=GROUP[ GROUP...]] - -## DESCRIPTION - -Prints a list of all the gems in the bundle including their version. - -Example: - -bundle list --name-only - -bundle list --paths - -bundle list --without-group test - -bundle list --only-group dev - -bundle list --only-group dev test --paths - -## OPTIONS - -* `--name-only`: - Print only the name of each gem. -* `--paths`: - Print the path to each gem in the bundle. -* `--without-group=<list>`: - A space-separated list of groups of gems to skip during printing. -* `--only-group=<list>`: - A space-separated list of groups of gems to print. diff --git a/man/bundle-lock.1 b/man/bundle-lock.1 deleted file mode 100644 index 350f1b3daa..0000000000 --- a/man/bundle-lock.1 +++ /dev/null @@ -1,84 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-LOCK" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-lock\fR \- Creates / Updates a lockfile without installing -. -.SH "SYNOPSIS" -\fBbundle lock\fR [\-\-update] [\-\-local] [\-\-print] [\-\-lockfile=PATH] [\-\-full\-index] [\-\-add\-platform] [\-\-remove\-platform] [\-\-patch] [\-\-minor] [\-\-major] [\-\-strict] [\-\-conservative] -. -.SH "DESCRIPTION" -Lock the gems specified in Gemfile\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-update=<*gems>\fR -Ignores the existing lockfile\. Resolve then updates lockfile\. Taking a list of gems or updating all gems if no list is given\. -. -.TP -\fB\-\-local\fR -Do not attempt to connect to \fBrubygems\.org\fR\. Instead, Bundler will use the gems already present in Rubygems\' cache or in \fBvendor/cache\fR\. Note that if a appropriate platform\-specific gem exists on \fBrubygems\.org\fR it will not be found\. -. -.TP -\fB\-\-print\fR -Prints the lockfile to STDOUT instead of writing to the file system\. -. -.TP -\fB\-\-lockfile=<path>\fR -The path where the lockfile should be written to\. -. -.TP -\fB\-\-full\-index\fR -Fall back to using the single\-file index of all gems\. -. -.TP -\fB\-\-add\-platform\fR -Add a new platform to the lockfile, re\-resolving for the addition of that platform\. -. -.TP -\fB\-\-remove\-platform\fR -Remove a platform from the lockfile\. -. -.TP -\fB\-\-patch\fR -If updating, prefer updating only to next patch version\. -. -.TP -\fB\-\-minor\fR -If updating, prefer updating only to next minor version\. -. -.TP -\fB\-\-major\fR -If updating, prefer updating to next major version (default)\. -. -.TP -\fB\-\-strict\fR -If updating, do not allow any gem to be updated past latest \-\-patch | \-\-minor | \-\-major\. -. -.TP -\fB\-\-conservative\fR -If updating, use bundle install conservative update behavior and do not allow shared dependencies to be updated\. -. -.SH "UPDATING ALL GEMS" -If you run \fBbundle lock\fR with \fB\-\-update\fR option without list of gems, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\. -. -.SH "UPDATING A LIST OF GEMS" -Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the gems that you specified locked to the versions in the \fBGemfile\.lock\fR\. -. -.P -For instance, you only want to update \fBnokogiri\fR, run \fBbundle lock \-\-update nokogiri\fR\. -. -.P -Bundler will update \fBnokogiri\fR and any of its dependencies, but leave the rest of the gems that you specified locked to the versions in the \fBGemfile\.lock\fR\. -. -.SH "SUPPORTING OTHER PLATFORMS" -If you want your bundle to support platforms other than the one you\'re running locally, you can run \fBbundle lock \-\-add\-platform PLATFORM\fR to add PLATFORM to the lockfile, force bundler to re\-resolve and consider the new platform when picking gems, all without needing to have a machine that matches PLATFORM handy to install those platform\-specific gems on\. -. -.P -For a full explanation of gem platforms, see \fBgem help platform\fR\. -. -.SH "PATCH LEVEL OPTIONS" -See bundle update(1) \fIbundle\-update\.1\.html\fR for details\. diff --git a/man/bundle-lock.1.ronn b/man/bundle-lock.1.ronn deleted file mode 100644 index 3aa5920f5a..0000000000 --- a/man/bundle-lock.1.ronn +++ /dev/null @@ -1,94 +0,0 @@ -bundle-lock(1) -- Creates / Updates a lockfile without installing -================================================================= - -## SYNOPSIS - -`bundle lock` [--update] - [--local] - [--print] - [--lockfile=PATH] - [--full-index] - [--add-platform] - [--remove-platform] - [--patch] - [--minor] - [--major] - [--strict] - [--conservative] - -## DESCRIPTION - -Lock the gems specified in Gemfile. - -## OPTIONS - -* `--update=<*gems>`: - Ignores the existing lockfile. Resolve then updates lockfile. Taking a list - of gems or updating all gems if no list is given. - -* `--local`: - Do not attempt to connect to `rubygems.org`. Instead, Bundler will use the - gems already present in Rubygems' cache or in `vendor/cache`. Note that if a - appropriate platform-specific gem exists on `rubygems.org` it will not be - found. - -* `--print`: - Prints the lockfile to STDOUT instead of writing to the file system. - -* `--lockfile=<path>`: - The path where the lockfile should be written to. - -* `--full-index`: - Fall back to using the single-file index of all gems. - -* `--add-platform`: - Add a new platform to the lockfile, re-resolving for the addition of that - platform. - -* `--remove-platform`: - Remove a platform from the lockfile. - -* `--patch`: - If updating, prefer updating only to next patch version. - -* `--minor`: - If updating, prefer updating only to next minor version. - -* `--major`: - If updating, prefer updating to next major version (default). - -* `--strict`: - If updating, do not allow any gem to be updated past latest --patch | --minor | --major. - -* `--conservative`: - If updating, use bundle install conservative update behavior and do not allow shared dependencies to be updated. - -## UPDATING ALL GEMS - -If you run `bundle lock` with `--update` option without list of gems, bundler will -ignore any previously installed gems and resolve all dependencies again based -on the latest versions of all gems available in the sources. - -## UPDATING A LIST OF GEMS - -Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of -the gems that you specified locked to the versions in the `Gemfile.lock`. - -For instance, you only want to update `nokogiri`, run `bundle lock --update nokogiri`. - -Bundler will update `nokogiri` and any of its dependencies, but leave the rest of the -gems that you specified locked to the versions in the `Gemfile.lock`. - -## SUPPORTING OTHER PLATFORMS - -If you want your bundle to support platforms other than the one you're running -locally, you can run `bundle lock --add-platform PLATFORM` to add PLATFORM to -the lockfile, force bundler to re-resolve and consider the new platform when -picking gems, all without needing to have a machine that matches PLATFORM handy -to install those platform-specific gems on. - -For a full explanation of gem platforms, see `gem help platform`. - -## PATCH LEVEL OPTIONS - -See [bundle update(1)](bundle-update.1.html) for details. diff --git a/man/bundle-open.1 b/man/bundle-open.1 deleted file mode 100644 index 9986d5004c..0000000000 --- a/man/bundle-open.1 +++ /dev/null @@ -1,32 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-OPEN" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-open\fR \- Opens the source directory for a gem in your bundle -. -.SH "SYNOPSIS" -\fBbundle open\fR [GEM] -. -.SH "DESCRIPTION" -Opens the source directory of the provided GEM in your editor\. -. -.P -For this to work the \fBEDITOR\fR or \fBBUNDLER_EDITOR\fR environment variable has to be set\. -. -.P -Example: -. -.IP "" 4 -. -.nf - -bundle open \'rack\' -. -.fi -. -.IP "" 0 -. -.P -Will open the source directory for the \'rack\' gem in your bundle\. diff --git a/man/bundle-open.1.ronn b/man/bundle-open.1.ronn deleted file mode 100644 index 497beac93f..0000000000 --- a/man/bundle-open.1.ronn +++ /dev/null @@ -1,19 +0,0 @@ -bundle-open(1) -- Opens the source directory for a gem in your bundle -===================================================================== - -## SYNOPSIS - -`bundle open` [GEM] - -## DESCRIPTION - -Opens the source directory of the provided GEM in your editor. - -For this to work the `EDITOR` or `BUNDLER_EDITOR` environment variable has to -be set. - -Example: - - bundle open 'rack' - -Will open the source directory for the 'rack' gem in your bundle. diff --git a/man/bundle-outdated.1 b/man/bundle-outdated.1 deleted file mode 100644 index 3fc3cdc601..0000000000 --- a/man/bundle-outdated.1 +++ /dev/null @@ -1,155 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-OUTDATED" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-outdated\fR \- List installed gems with newer versions available -. -.SH "SYNOPSIS" -\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-update\-strict] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch] [\-\-only\-explicit] -. -.SH "DESCRIPTION" -Outdated lists the names and versions of gems that have a newer version available in the given source\. Calling outdated with [GEM [GEM]] will only check for newer versions of the given gems\. Prerelease gems are ignored by default\. If your gems are up to date, Bundler will exit with a status of 0\. Otherwise, it will exit 1\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-local\fR -Do not attempt to fetch gems remotely and use the gem cache instead\. -. -.TP -\fB\-\-pre\fR -Check for newer pre\-release gems\. -. -.TP -\fB\-\-source\fR -Check against a specific source\. -. -.TP -\fB\-\-strict\fR -Only list newer versions allowed by your Gemfile requirements\. -. -.TP -\fB\-\-parseable\fR, \fB\-\-porcelain\fR -Use minimal formatting for more parseable output\. -. -.TP -\fB\-\-group\fR -List gems from a specific group\. -. -.TP -\fB\-\-groups\fR -List gems organized by groups\. -. -.TP -\fB\-\-update\-strict\fR -Strict conservative resolution, do not allow any gem to be updated past latest \-\-patch | \-\-minor| \-\-major\. -. -.TP -\fB\-\-minor\fR -Prefer updating only to next minor version\. -. -.TP -\fB\-\-major\fR -Prefer updating to next major version (default)\. -. -.TP -\fB\-\-patch\fR -Prefer updating only to next patch version\. -. -.TP -\fB\-\-filter\-major\fR -Only list major newer versions\. -. -.TP -\fB\-\-filter\-minor\fR -Only list minor newer versions\. -. -.TP -\fB\-\-filter\-patch\fR -Only list patch newer versions\. -. -.TP -\fB\-\-only\-explicit\fR -Only list gems specified in your Gemfile, not their dependencies\. -. -.SH "PATCH LEVEL OPTIONS" -See bundle update(1) \fIbundle\-update\.1\.html\fR for details\. -. -.P -One difference between the patch level options in \fBbundle update\fR and here is the \fB\-\-strict\fR option\. \fB\-\-strict\fR was already an option on outdated before the patch level options were added\. \fB\-\-strict\fR wasn\'t altered, and the \fB\-\-update\-strict\fR option on \fBoutdated\fR reflects what \fB\-\-strict\fR does on \fBbundle update\fR\. -. -.SH "FILTERING OUTPUT" -The 3 filtering options do not affect the resolution of versions, merely what versions are shown in the output\. -. -.P -If the regular output shows the following: -. -.IP "" 4 -. -.nf - -* faker (newest 1\.6\.6, installed 1\.6\.5, requested ~> 1\.4) in groups "development, test" -* hashie (newest 3\.4\.6, installed 1\.2\.0, requested = 1\.2\.0) in groups "default" -* headless (newest 2\.3\.1, installed 2\.2\.3) in groups "test" -. -.fi -. -.IP "" 0 -. -.P -\fB\-\-filter\-major\fR would only show: -. -.IP "" 4 -. -.nf - -* hashie (newest 3\.4\.6, installed 1\.2\.0, requested = 1\.2\.0) in groups "default" -. -.fi -. -.IP "" 0 -. -.P -\fB\-\-filter\-minor\fR would only show: -. -.IP "" 4 -. -.nf - -* headless (newest 2\.3\.1, installed 2\.2\.3) in groups "test" -. -.fi -. -.IP "" 0 -. -.P -\fB\-\-filter\-patch\fR would only show: -. -.IP "" 4 -. -.nf - -* faker (newest 1\.6\.6, installed 1\.6\.5, requested ~> 1\.4) in groups "development, test" -. -.fi -. -.IP "" 0 -. -.P -Filter options can be combined\. \fB\-\-filter\-minor\fR and \fB\-\-filter\-patch\fR would show: -. -.IP "" 4 -. -.nf - -* faker (newest 1\.6\.6, installed 1\.6\.5, requested ~> 1\.4) in groups "development, test" -* headless (newest 2\.3\.1, installed 2\.2\.3) in groups "test" -. -.fi -. -.IP "" 0 -. -.P -Combining all three \fBfilter\fR options would be the same result as providing none of them\. diff --git a/man/bundle-outdated.1.ronn b/man/bundle-outdated.1.ronn deleted file mode 100644 index a991d23789..0000000000 --- a/man/bundle-outdated.1.ronn +++ /dev/null @@ -1,111 +0,0 @@ -bundle-outdated(1) -- List installed gems with newer versions available -======================================================================= - -## SYNOPSIS - -`bundle outdated` [GEM] [--local] - [--pre] - [--source] - [--strict] - [--parseable | --porcelain] - [--group=GROUP] - [--groups] - [--update-strict] - [--patch|--minor|--major] - [--filter-major] - [--filter-minor] - [--filter-patch] - [--only-explicit] - -## DESCRIPTION - -Outdated lists the names and versions of gems that have a newer version available -in the given source. Calling outdated with [GEM [GEM]] will only check for newer -versions of the given gems. Prerelease gems are ignored by default. If your gems -are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1. - -## OPTIONS - -* `--local`: - Do not attempt to fetch gems remotely and use the gem cache instead. - -* `--pre`: - Check for newer pre-release gems. - -* `--source`: - Check against a specific source. - -* `--strict`: - Only list newer versions allowed by your Gemfile requirements. - -* `--parseable`, `--porcelain`: - Use minimal formatting for more parseable output. - -* `--group`: - List gems from a specific group. - -* `--groups`: - List gems organized by groups. - -* `--update-strict`: - Strict conservative resolution, do not allow any gem to be updated past latest --patch | --minor| --major. - -* `--minor`: - Prefer updating only to next minor version. - -* `--major`: - Prefer updating to next major version (default). - -* `--patch`: - Prefer updating only to next patch version. - -* `--filter-major`: - Only list major newer versions. - -* `--filter-minor`: - Only list minor newer versions. - -* `--filter-patch`: - Only list patch newer versions. - -* `--only-explicit`: - Only list gems specified in your Gemfile, not their dependencies. - -## PATCH LEVEL OPTIONS - -See [bundle update(1)](bundle-update.1.html) for details. - -One difference between the patch level options in `bundle update` and here is the `--strict` option. -`--strict` was already an option on outdated before the patch level options were added. `--strict` -wasn't altered, and the `--update-strict` option on `outdated` reflects what `--strict` does on -`bundle update`. - -## FILTERING OUTPUT - -The 3 filtering options do not affect the resolution of versions, merely what versions are shown -in the output. - -If the regular output shows the following: - - * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test" - * hashie (newest 3.4.6, installed 1.2.0, requested = 1.2.0) in groups "default" - * headless (newest 2.3.1, installed 2.2.3) in groups "test" - -`--filter-major` would only show: - - * hashie (newest 3.4.6, installed 1.2.0, requested = 1.2.0) in groups "default" - -`--filter-minor` would only show: - - * headless (newest 2.3.1, installed 2.2.3) in groups "test" - -`--filter-patch` would only show: - - * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test" - -Filter options can be combined. `--filter-minor` and `--filter-patch` would show: - - * faker (newest 1.6.6, installed 1.6.5, requested ~> 1.4) in groups "development, test" - * headless (newest 2.3.1, installed 2.2.3) in groups "test" - -Combining all three `filter` options would be the same result as providing none of them. diff --git a/man/bundle-platform.1 b/man/bundle-platform.1 deleted file mode 100644 index b4c521e0c1..0000000000 --- a/man/bundle-platform.1 +++ /dev/null @@ -1,61 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-PLATFORM" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-platform\fR \- Displays platform compatibility information -. -.SH "SYNOPSIS" -\fBbundle platform\fR [\-\-ruby] -. -.SH "DESCRIPTION" -\fBplatform\fR will display information from your Gemfile, Gemfile\.lock, and Ruby VM about your platform\. -. -.P -For instance, using this Gemfile(5): -. -.IP "" 4 -. -.nf - -source "https://rubygems\.org" - -ruby "1\.9\.3" - -gem "rack" -. -.fi -. -.IP "" 0 -. -.P -If you run \fBbundle platform\fR on Ruby 1\.9\.3, it will display the following output: -. -.IP "" 4 -. -.nf - -Your platform is: x86_64\-linux - -Your app has gems that work on these platforms: -* ruby - -Your Gemfile specifies a Ruby version requirement: -* ruby 1\.9\.3 - -Your current platform satisfies the Ruby version requirement\. -. -.fi -. -.IP "" 0 -. -.P -\fBplatform\fR will list all the platforms in your \fBGemfile\.lock\fR as well as the \fBruby\fR directive if applicable from your Gemfile(5)\. It will also let you know if the \fBruby\fR directive requirement has been met\. If \fBruby\fR directive doesn\'t match the running Ruby VM, it will tell you what part does not\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-ruby\fR -It will display the ruby directive information, so you don\'t have to parse it from the Gemfile(5)\. - diff --git a/man/bundle-platform.1.ronn b/man/bundle-platform.1.ronn deleted file mode 100644 index b5d3283fb6..0000000000 --- a/man/bundle-platform.1.ronn +++ /dev/null @@ -1,42 +0,0 @@ -bundle-platform(1) -- Displays platform compatibility information -================================================================= - -## SYNOPSIS - -`bundle platform` [--ruby] - -## DESCRIPTION - -`platform` will display information from your Gemfile, Gemfile.lock, and Ruby -VM about your platform. - -For instance, using this Gemfile(5): - - source "https://rubygems.org" - - ruby "1.9.3" - - gem "rack" - -If you run `bundle platform` on Ruby 1.9.3, it will display the following output: - - Your platform is: x86_64-linux - - Your app has gems that work on these platforms: - * ruby - - Your Gemfile specifies a Ruby version requirement: - * ruby 1.9.3 - - Your current platform satisfies the Ruby version requirement. - -`platform` will list all the platforms in your `Gemfile.lock` as well as the -`ruby` directive if applicable from your Gemfile(5). It will also let you know -if the `ruby` directive requirement has been met. If `ruby` directive doesn't -match the running Ruby VM, it will tell you what part does not. - -## OPTIONS - -* `--ruby`: - It will display the ruby directive information, so you don't have to - parse it from the Gemfile(5). diff --git a/man/bundle-pristine.1 b/man/bundle-pristine.1 deleted file mode 100644 index 0a1790655e..0000000000 --- a/man/bundle-pristine.1 +++ /dev/null @@ -1,34 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-PRISTINE" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-pristine\fR \- Restores installed gems to their pristine condition -. -.SH "SYNOPSIS" -\fBbundle pristine\fR -. -.SH "DESCRIPTION" -\fBpristine\fR restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems\. For git gems, a forced checkout will be performed\. -. -.P -For further explanation, \fBbundle pristine\fR ignores unpacked files on disk\. In other words, this command utilizes the local \fB\.gem\fR cache or the gem\'s git repository as if one were installing from scratch\. -. -.P -Note: the Bundler gem cannot be restored to its original state with \fBpristine\fR\. One also cannot use \fBbundle pristine\fR on gems with a \'path\' option in the Gemfile, because bundler has no original copy it can restore from\. -. -.P -When is it practical to use \fBbundle pristine\fR? -. -.P -It comes in handy when a developer is debugging a gem\. \fBbundle pristine\fR is a great way to get rid of experimental changes to a gem that one may not want\. -. -.P -Why use \fBbundle pristine\fR over \fBgem pristine \-\-all\fR? -. -.P -Both commands are very similar\. For context: \fBbundle pristine\fR, without arguments, cleans all gems from the lockfile\. Meanwhile, \fBgem pristine \-\-all\fR cleans all installed gems for that Ruby version\. -. -.P -If a developer forgets which gems in their project they might have been debugging, the Rubygems \fBgem pristine [GEMNAME]\fR command may be inconvenient\. One can avoid waiting for \fBgem pristine \-\-all\fR, and instead run \fBbundle pristine\fR\. diff --git a/man/bundle-pristine.1.ronn b/man/bundle-pristine.1.ronn deleted file mode 100644 index e2d6b6a348..0000000000 --- a/man/bundle-pristine.1.ronn +++ /dev/null @@ -1,34 +0,0 @@ -bundle-pristine(1) -- Restores installed gems to their pristine condition -=========================================================================== - -## SYNOPSIS - -`bundle pristine` - -## DESCRIPTION - -`pristine` restores the installed gems in the bundle to their pristine condition -using the local gem cache from RubyGems. For git gems, a forced checkout will be performed. - -For further explanation, `bundle pristine` ignores unpacked files on disk. In other -words, this command utilizes the local `.gem` cache or the gem's git repository -as if one were installing from scratch. - -Note: the Bundler gem cannot be restored to its original state with `pristine`. -One also cannot use `bundle pristine` on gems with a 'path' option in the Gemfile, -because bundler has no original copy it can restore from. - -When is it practical to use `bundle pristine`? - -It comes in handy when a developer is debugging a gem. `bundle pristine` is a -great way to get rid of experimental changes to a gem that one may not want. - -Why use `bundle pristine` over `gem pristine --all`? - -Both commands are very similar. -For context: `bundle pristine`, without arguments, cleans all gems from the lockfile. -Meanwhile, `gem pristine --all` cleans all installed gems for that Ruby version. - -If a developer forgets which gems in their project they might -have been debugging, the Rubygems `gem pristine [GEMNAME]` command may be inconvenient. -One can avoid waiting for `gem pristine --all`, and instead run `bundle pristine`. diff --git a/man/bundle-remove.1 b/man/bundle-remove.1 deleted file mode 100644 index ee24f676a6..0000000000 --- a/man/bundle-remove.1 +++ /dev/null @@ -1,31 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-REMOVE" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-remove\fR \- Removes gems from the Gemfile -. -.SH "SYNOPSIS" -\fBbundle remove [GEM [GEM \.\.\.]] [\-\-install]\fR -. -.SH "DESCRIPTION" -Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid\. If a gem cannot be removed, a warning is printed\. If a gem is already absent from the Gemfile, and error is raised\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-install\fR -Runs \fBbundle install\fR after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s)\. -. -.P -Example: -. -.P -bundle remove rails -. -.P -bundle remove rails rack -. -.P -bundle remove rails rack \-\-install diff --git a/man/bundle-remove.1.ronn b/man/bundle-remove.1.ronn deleted file mode 100644 index 40a239b4a2..0000000000 --- a/man/bundle-remove.1.ronn +++ /dev/null @@ -1,23 +0,0 @@ -bundle-remove(1) -- Removes gems from the Gemfile -=========================================================================== - -## SYNOPSIS - -`bundle remove [GEM [GEM ...]] [--install]` - -## DESCRIPTION - -Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid. If a gem cannot be removed, a warning is printed. If a gem is already absent from the Gemfile, and error is raised. - -## OPTIONS - -* `--install`: - Runs `bundle install` after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s). - -Example: - -bundle remove rails - -bundle remove rails rack - -bundle remove rails rack --install diff --git a/man/bundle-show.1 b/man/bundle-show.1 deleted file mode 100644 index f83c810ffe..0000000000 --- a/man/bundle-show.1 +++ /dev/null @@ -1,23 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-SHOW" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem -. -.SH "SYNOPSIS" -\fBbundle show\fR [GEM] [\-\-paths] -. -.SH "DESCRIPTION" -Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)], sorted by name\. -. -.P -Calling show with [GEM] will list the exact location of that gem on your machine\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-paths\fR -List the paths of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)], sorted by gem name\. - diff --git a/man/bundle-show.1.ronn b/man/bundle-show.1.ronn deleted file mode 100644 index a6a59a1445..0000000000 --- a/man/bundle-show.1.ronn +++ /dev/null @@ -1,21 +0,0 @@ -bundle-show(1) -- Shows all the gems in your bundle, or the path to a gem -========================================================================= - -## SYNOPSIS - -`bundle show` [GEM] - [--paths] - -## DESCRIPTION - -Without the [GEM] option, `show` will print a list of the names and versions of -all gems that are required by your [`Gemfile(5)`][Gemfile(5)], sorted by name. - -Calling show with [GEM] will list the exact location of that gem on your -machine. - -## OPTIONS - -* `--paths`: - List the paths of all gems that are required by your [`Gemfile(5)`][Gemfile(5)], - sorted by gem name. diff --git a/man/bundle-update.1 b/man/bundle-update.1 deleted file mode 100644 index 002f2e69b9..0000000000 --- a/man/bundle-update.1 +++ /dev/null @@ -1,394 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-UPDATE" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-update\fR \- Update your gems to the latest available versions -. -.SH "SYNOPSIS" -\fBbundle update\fR \fI*gems\fR [\-\-all] [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-patch|\-\-minor|\-\-major] [\-\-redownload] [\-\-strict] [\-\-conservative] -. -.SH "DESCRIPTION" -Update the gems specified (all gems, if \fB\-\-all\fR flag is used), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use bundle install(1) \fIbundle\-install\.1\.html\fR to install the same exact gems and versions across machines\. -. -.P -You would use \fBbundle update\fR to explicitly update the version of a gem\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-all\fR -Update all gems specified in Gemfile\. -. -.TP -\fB\-\-group=<name>\fR, \fB\-g=[<name>]\fR -Only update the gems in the specified group\. For instance, you can update all gems in the development group with \fBbundle update \-\-group development\fR\. You can also call \fBbundle update rails \-\-group test\fR to update the rails gem and all gems in the test group, for example\. -. -.TP -\fB\-\-source=<name>\fR -The name of a \fB:git\fR or \fB:path\fR source used in the Gemfile(5)\. For instance, with a \fB:git\fR source of \fBhttp://github\.com/rails/rails\.git\fR, you would call \fBbundle update \-\-source rails\fR -. -.TP -\fB\-\-local\fR -Do not attempt to fetch gems remotely and use the gem cache instead\. -. -.TP -\fB\-\-ruby\fR -Update the locked version of Ruby to the current version of Ruby\. -. -.TP -\fB\-\-bundler\fR -Update the locked version of bundler to the invoked bundler version\. -. -.TP -\fB\-\-full\-index\fR -Fall back to using the single\-file index of all gems\. -. -.TP -\fB\-\-jobs=[<number>]\fR, \fB\-j[<number>]\fR -Specify the number of jobs to run in parallel\. The default is \fB1\fR\. -. -.TP -\fB\-\-retry=[<number>]\fR -Retry failed network or git requests for \fInumber\fR times\. -. -.TP -\fB\-\-quiet\fR -Only output warnings and errors\. -. -.TP -\fB\-\-redownload\fR -Force downloading every gem\. -. -.TP -\fB\-\-patch\fR -Prefer updating only to next patch version\. -. -.TP -\fB\-\-minor\fR -Prefer updating only to next minor version\. -. -.TP -\fB\-\-major\fR -Prefer updating to next major version (default)\. -. -.TP -\fB\-\-strict\fR -Do not allow any gem to be updated past latest \fB\-\-patch\fR | \fB\-\-minor\fR | \fB\-\-major\fR\. -. -.TP -\fB\-\-conservative\fR -Use bundle install conservative update behavior and do not allow shared dependencies to be updated\. -. -.SH "UPDATING ALL GEMS" -If you run \fBbundle update \-\-all\fR, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\. -. -.P -Consider the following Gemfile(5): -. -.IP "" 4 -. -.nf - -source "https://rubygems\.org" - -gem "rails", "3\.0\.0\.rc" -gem "nokogiri" -. -.fi -. -.IP "" 0 -. -.P -When you run bundle install(1) \fIbundle\-install\.1\.html\fR the first time, bundler will resolve all of the dependencies, all the way down, and install what you need: -. -.IP "" 4 -. -.nf - -Fetching gem metadata from https://rubygems\.org/\.\.\.\.\.\.\.\.\. -Resolving dependencies\.\.\. -Installing builder 2\.1\.2 -Installing abstract 1\.0\.0 -Installing rack 1\.2\.8 -Using bundler 1\.7\.6 -Installing rake 10\.4\.0 -Installing polyglot 0\.3\.5 -Installing mime\-types 1\.25\.1 -Installing i18n 0\.4\.2 -Installing mini_portile 0\.6\.1 -Installing tzinfo 0\.3\.42 -Installing rack\-mount 0\.6\.14 -Installing rack\-test 0\.5\.7 -Installing treetop 1\.4\.15 -Installing thor 0\.14\.6 -Installing activesupport 3\.0\.0\.rc -Installing erubis 2\.6\.6 -Installing activemodel 3\.0\.0\.rc -Installing arel 0\.4\.0 -Installing mail 2\.2\.20 -Installing activeresource 3\.0\.0\.rc -Installing actionpack 3\.0\.0\.rc -Installing activerecord 3\.0\.0\.rc -Installing actionmailer 3\.0\.0\.rc -Installing railties 3\.0\.0\.rc -Installing rails 3\.0\.0\.rc -Installing nokogiri 1\.6\.5 - -Bundle complete! 2 Gemfile dependencies, 26 gems total\. -Use `bundle show [gemname]` to see where a bundled gem is installed\. -. -.fi -. -.IP "" 0 -. -.P -As you can see, even though you have two gems in the Gemfile(5), your application needs 26 different gems in order to run\. Bundler remembers the exact versions it installed in \fBGemfile\.lock\fR\. The next time you run bundle install(1) \fIbundle\-install\.1\.html\fR, bundler skips the dependency resolution and installs the same gems as it installed last time\. -. -.P -After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running bundle install(1) \fIbundle\-install\.1\.html\fR will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\. -. -.P -However, from time to time, you might want to update the gems you are using to the newest versions that still match the gems in your Gemfile(5)\. -. -.P -To do this, run \fBbundle update \-\-all\fR, which will ignore the \fBGemfile\.lock\fR, and resolve all the dependencies again\. Keep in mind that this process can result in a significantly different set of the 25 gems, based on the requirements of new gems that the gem authors released since the last time you ran \fBbundle update \-\-all\fR\. -. -.SH "UPDATING A LIST OF GEMS" -Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the gems that you specified locked to the versions in the \fBGemfile\.lock\fR\. -. -.P -For instance, in the scenario above, imagine that \fBnokogiri\fR releases version \fB1\.4\.4\fR, and you want to update it \fIwithout\fR updating Rails and all of its dependencies\. To do this, run \fBbundle update nokogiri\fR\. -. -.P -Bundler will update \fBnokogiri\fR and any of its dependencies, but leave alone Rails and its dependencies\. -. -.SH "OVERLAPPING DEPENDENCIES" -Sometimes, multiple gems declared in your Gemfile(5) are satisfied by the same second\-level dependency\. For instance, consider the case of \fBthin\fR and \fBrack\-perftools\-profiler\fR\. -. -.IP "" 4 -. -.nf - -source "https://rubygems\.org" - -gem "thin" -gem "rack\-perftools\-profiler" -. -.fi -. -.IP "" 0 -. -.P -The \fBthin\fR gem depends on \fBrack >= 1\.0\fR, while \fBrack\-perftools\-profiler\fR depends on \fBrack ~> 1\.0\fR\. If you run bundle install, you get: -. -.IP "" 4 -. -.nf - -Fetching source index for https://rubygems\.org/ -Installing daemons (1\.1\.0) -Installing eventmachine (0\.12\.10) with native extensions -Installing open4 (1\.0\.1) -Installing perftools\.rb (0\.4\.7) with native extensions -Installing rack (1\.2\.1) -Installing rack\-perftools_profiler (0\.0\.2) -Installing thin (1\.2\.7) with native extensions -Using bundler (1\.0\.0\.rc\.3) -. -.fi -. -.IP "" 0 -. -.P -In this case, the two gems have their own set of dependencies, but they share \fBrack\fR in common\. If you run \fBbundle update thin\fR, bundler will update \fBdaemons\fR, \fBeventmachine\fR and \fBrack\fR, which are dependencies of \fBthin\fR, but not \fBopen4\fR or \fBperftools\.rb\fR, which are dependencies of \fBrack\-perftools_profiler\fR\. Note that \fBbundle update thin\fR will update \fBrack\fR even though it\'s \fIalso\fR a dependency of \fBrack\-perftools_profiler\fR\. -. -.P -In short, by default, when you update a gem using \fBbundle update\fR, bundler will update all dependencies of that gem, including those that are also dependencies of another gem\. -. -.P -To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in bundle install(1) \fIbundle\-install\.1\.html\fR: -. -.P -In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running bundle install(1) \fIbundle\-install\.1\.html\fR will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of bundle install(1) \fIbundle\-install\.1\.html\fR\. -. -.P -Starting with 1\.14, specifying the \fB\-\-conservative\fR option will also prevent shared dependencies from being updated\. -. -.SH "PATCH LEVEL OPTIONS" -Version 1\.14 introduced 4 patch\-level options that will influence how gem versions are resolved\. One of the following options can be used: \fB\-\-patch\fR, \fB\-\-minor\fR or \fB\-\-major\fR\. \fB\-\-strict\fR can be added to further influence resolution\. -. -.TP -\fB\-\-patch\fR -Prefer updating only to next patch version\. -. -.TP -\fB\-\-minor\fR -Prefer updating only to next minor version\. -. -.TP -\fB\-\-major\fR -Prefer updating to next major version (default)\. -. -.TP -\fB\-\-strict\fR -Do not allow any gem to be updated past latest \fB\-\-patch\fR | \fB\-\-minor\fR | \fB\-\-major\fR\. -. -.P -When Bundler is resolving what versions to use to satisfy declared requirements in the Gemfile or in parent gems, it looks up all available versions, filters out any versions that don\'t satisfy the requirement, and then, by default, sorts them from newest to oldest, considering them in that order\. -. -.P -Providing one of the patch level options (e\.g\. \fB\-\-patch\fR) changes the sort order of the satisfying versions, causing Bundler to consider the latest \fB\-\-patch\fR or \fB\-\-minor\fR version available before other versions\. Note that versions outside the stated patch level could still be resolved to if necessary to find a suitable dependency graph\. -. -.P -For example, if gem \'foo\' is locked at 1\.0\.2, with no gem requirement defined in the Gemfile, and versions 1\.0\.3, 1\.0\.4, 1\.1\.0, 1\.1\.1, 2\.0\.0 all exist, the default order of preference by default (\fB\-\-major\fR) will be "2\.0\.0, 1\.1\.1, 1\.1\.0, 1\.0\.4, 1\.0\.3, 1\.0\.2"\. -. -.P -If the \fB\-\-patch\fR option is used, the order of preference will change to "1\.0\.4, 1\.0\.3, 1\.0\.2, 1\.1\.1, 1\.1\.0, 2\.0\.0"\. -. -.P -If the \fB\-\-minor\fR option is used, the order of preference will change to "1\.1\.1, 1\.1\.0, 1\.0\.4, 1\.0\.3, 1\.0\.2, 2\.0\.0"\. -. -.P -Combining the \fB\-\-strict\fR option with any of the patch level options will remove any versions beyond the scope of the patch level option, to ensure that no gem is updated that far\. -. -.P -To continue the previous example, if both \fB\-\-patch\fR and \fB\-\-strict\fR options are used, the available versions for resolution would be "1\.0\.4, 1\.0\.3, 1\.0\.2"\. If \fB\-\-minor\fR and \fB\-\-strict\fR are used, it would be "1\.1\.1, 1\.1\.0, 1\.0\.4, 1\.0\.3, 1\.0\.2"\. -. -.P -Gem requirements as defined in the Gemfile will still be the first determining factor for what versions are available\. If the gem requirement for \fBfoo\fR in the Gemfile is \'~> 1\.0\', that will accomplish the same thing as providing the \fB\-\-minor\fR and \fB\-\-strict\fR options\. -. -.SH "PATCH LEVEL EXAMPLES" -Given the following gem specifications: -. -.IP "" 4 -. -.nf - -foo 1\.4\.3, requires: ~> bar 2\.0 -foo 1\.4\.4, requires: ~> bar 2\.0 -foo 1\.4\.5, requires: ~> bar 2\.1 -foo 1\.5\.0, requires: ~> bar 2\.1 -foo 1\.5\.1, requires: ~> bar 3\.0 -bar with versions 2\.0\.3, 2\.0\.4, 2\.1\.0, 2\.1\.1, 3\.0\.0 -. -.fi -. -.IP "" 0 -. -.P -Gemfile: -. -.IP "" 4 -. -.nf - -gem \'foo\' -. -.fi -. -.IP "" 0 -. -.P -Gemfile\.lock: -. -.IP "" 4 -. -.nf - -foo (1\.4\.3) - bar (~> 2\.0) -bar (2\.0\.3) -. -.fi -. -.IP "" 0 -. -.P -Cases: -. -.IP "" 4 -. -.nf - -# Command Line Result -\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- -1 bundle update \-\-patch \'foo 1\.4\.5\', \'bar 2\.1\.1\' -2 bundle update \-\-patch foo \'foo 1\.4\.5\', \'bar 2\.1\.1\' -3 bundle update \-\-minor \'foo 1\.5\.1\', \'bar 3\.0\.0\' -4 bundle update \-\-minor \-\-strict \'foo 1\.5\.0\', \'bar 2\.1\.1\' -5 bundle update \-\-patch \-\-strict \'foo 1\.4\.4\', \'bar 2\.0\.4\' -. -.fi -. -.IP "" 0 -. -.P -In case 1, bar is upgraded to 2\.1\.1, a minor version increase, because the dependency from foo 1\.4\.5 required it\. -. -.P -In case 2, only foo is requested to be unlocked, but bar is also allowed to move because it\'s not a declared dependency in the Gemfile\. -. -.P -In case 3, bar goes up a whole major release, because a minor increase is preferred now for foo, and when it goes to 1\.5\.1, it requires 3\.0\.0 of bar\. -. -.P -In case 4, foo is preferred up to a minor version, but 1\.5\.1 won\'t work because the \-\-strict flag removes bar 3\.0\.0 from consideration since it\'s a major increment\. -. -.P -In case 5, both foo and bar have any minor or major increments removed from consideration because of the \-\-strict flag, so the most they can move is up to 1\.4\.4 and 2\.0\.4\. -. -.SH "RECOMMENDED WORKFLOW" -In general, when working with an application managed with bundler, you should use the following workflow: -. -.IP "\(bu" 4 -After you create your Gemfile(5) for the first time, run -. -.IP -$ bundle install -. -.IP "\(bu" 4 -Check the resulting \fBGemfile\.lock\fR into version control -. -.IP -$ git add Gemfile\.lock -. -.IP "\(bu" 4 -When checking out this repository on another development machine, run -. -.IP -$ bundle install -. -.IP "\(bu" 4 -When checking out this repository on a deployment machine, run -. -.IP -$ bundle install \-\-deployment -. -.IP "\(bu" 4 -After changing the Gemfile(5) to reflect a new or update dependency, run -. -.IP -$ bundle install -. -.IP "\(bu" 4 -Make sure to check the updated \fBGemfile\.lock\fR into version control -. -.IP -$ git add Gemfile\.lock -. -.IP "\(bu" 4 -If bundle install(1) \fIbundle\-install\.1\.html\fR reports a conflict, manually update the specific gems that you changed in the Gemfile(5) -. -.IP -$ bundle update rails thin -. -.IP "\(bu" 4 -If you want to update all the gems to the latest possible versions that still match the gems listed in the Gemfile(5), run -. -.IP -$ bundle update \-\-all -. -.IP "" 0 - diff --git a/man/bundle-update.1.ronn b/man/bundle-update.1.ronn deleted file mode 100644 index 397fecadcb..0000000000 --- a/man/bundle-update.1.ronn +++ /dev/null @@ -1,350 +0,0 @@ -bundle-update(1) -- Update your gems to the latest available versions -===================================================================== - -## SYNOPSIS - -`bundle update` <*gems> [--all] - [--group=NAME] - [--source=NAME] - [--local] - [--ruby] - [--bundler[=VERSION]] - [--full-index] - [--jobs=JOBS] - [--quiet] - [--patch|--minor|--major] - [--redownload] - [--strict] - [--conservative] - -## DESCRIPTION - -Update the gems specified (all gems, if `--all` flag is used), ignoring -the previously installed gems specified in the `Gemfile.lock`. In -general, you should use [bundle install(1)](bundle-install.1.html) to install the same exact -gems and versions across machines. - -You would use `bundle update` to explicitly update the version of a -gem. - -## OPTIONS - -* `--all`: - Update all gems specified in Gemfile. - -* `--group=<name>`, `-g=[<name>]`: - Only update the gems in the specified group. For instance, you can update all gems - in the development group with `bundle update --group development`. You can also - call `bundle update rails --group test` to update the rails gem and all gems in - the test group, for example. - -* `--source=<name>`: - The name of a `:git` or `:path` source used in the Gemfile(5). For - instance, with a `:git` source of `http://github.com/rails/rails.git`, - you would call `bundle update --source rails` - -* `--local`: - Do not attempt to fetch gems remotely and use the gem cache instead. - -* `--ruby`: - Update the locked version of Ruby to the current version of Ruby. - -* `--bundler`: - Update the locked version of bundler to the invoked bundler version. - -* `--full-index`: - Fall back to using the single-file index of all gems. - -* `--jobs=[<number>]`, `-j[<number>]`: - Specify the number of jobs to run in parallel. The default is `1`. - -* `--retry=[<number>]`: - Retry failed network or git requests for <number> times. - -* `--quiet`: - Only output warnings and errors. - -* `--redownload`: - Force downloading every gem. - -* `--patch`: - Prefer updating only to next patch version. - -* `--minor`: - Prefer updating only to next minor version. - -* `--major`: - Prefer updating to next major version (default). - -* `--strict`: - Do not allow any gem to be updated past latest `--patch` | `--minor` | `--major`. - -* `--conservative`: - Use bundle install conservative update behavior and do not allow shared dependencies to be updated. - -## UPDATING ALL GEMS - -If you run `bundle update --all`, bundler will ignore -any previously installed gems and resolve all dependencies again -based on the latest versions of all gems available in the sources. - -Consider the following Gemfile(5): - - source "https://rubygems.org" - - gem "rails", "3.0.0.rc" - gem "nokogiri" - -When you run [bundle install(1)](bundle-install.1.html) the first time, bundler will resolve -all of the dependencies, all the way down, and install what you need: - - Fetching gem metadata from https://rubygems.org/......... - Resolving dependencies... - Installing builder 2.1.2 - Installing abstract 1.0.0 - Installing rack 1.2.8 - Using bundler 1.7.6 - Installing rake 10.4.0 - Installing polyglot 0.3.5 - Installing mime-types 1.25.1 - Installing i18n 0.4.2 - Installing mini_portile 0.6.1 - Installing tzinfo 0.3.42 - Installing rack-mount 0.6.14 - Installing rack-test 0.5.7 - Installing treetop 1.4.15 - Installing thor 0.14.6 - Installing activesupport 3.0.0.rc - Installing erubis 2.6.6 - Installing activemodel 3.0.0.rc - Installing arel 0.4.0 - Installing mail 2.2.20 - Installing activeresource 3.0.0.rc - Installing actionpack 3.0.0.rc - Installing activerecord 3.0.0.rc - Installing actionmailer 3.0.0.rc - Installing railties 3.0.0.rc - Installing rails 3.0.0.rc - Installing nokogiri 1.6.5 - - Bundle complete! 2 Gemfile dependencies, 26 gems total. - Use `bundle show [gemname]` to see where a bundled gem is installed. - -As you can see, even though you have two gems in the Gemfile(5), your application -needs 26 different gems in order to run. Bundler remembers the exact versions -it installed in `Gemfile.lock`. The next time you run [bundle install(1)](bundle-install.1.html), bundler skips -the dependency resolution and installs the same gems as it installed last time. - -After checking in the `Gemfile.lock` into version control and cloning it on another -machine, running [bundle install(1)](bundle-install.1.html) will _still_ install the gems that you installed -last time. You don't need to worry that a new release of `erubis` or `mail` changes -the gems you use. - -However, from time to time, you might want to update the gems you are using to the -newest versions that still match the gems in your Gemfile(5). - -To do this, run `bundle update --all`, which will ignore the `Gemfile.lock`, and resolve -all the dependencies again. Keep in mind that this process can result in a significantly -different set of the 25 gems, based on the requirements of new gems that the gem -authors released since the last time you ran `bundle update --all`. - -## UPDATING A LIST OF GEMS - -Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the -gems that you specified locked to the versions in the `Gemfile.lock`. - -For instance, in the scenario above, imagine that `nokogiri` releases version `1.4.4`, and -you want to update it _without_ updating Rails and all of its dependencies. To do this, -run `bundle update nokogiri`. - -Bundler will update `nokogiri` and any of its dependencies, but leave alone Rails and -its dependencies. - -## OVERLAPPING DEPENDENCIES - -Sometimes, multiple gems declared in your Gemfile(5) are satisfied by the same -second-level dependency. For instance, consider the case of `thin` and -`rack-perftools-profiler`. - - source "https://rubygems.org" - - gem "thin" - gem "rack-perftools-profiler" - -The `thin` gem depends on `rack >= 1.0`, while `rack-perftools-profiler` depends -on `rack ~> 1.0`. If you run bundle install, you get: - - Fetching source index for https://rubygems.org/ - Installing daemons (1.1.0) - Installing eventmachine (0.12.10) with native extensions - Installing open4 (1.0.1) - Installing perftools.rb (0.4.7) with native extensions - Installing rack (1.2.1) - Installing rack-perftools_profiler (0.0.2) - Installing thin (1.2.7) with native extensions - Using bundler (1.0.0.rc.3) - -In this case, the two gems have their own set of dependencies, but they share -`rack` in common. If you run `bundle update thin`, bundler will update `daemons`, -`eventmachine` and `rack`, which are dependencies of `thin`, but not `open4` or -`perftools.rb`, which are dependencies of `rack-perftools_profiler`. Note that -`bundle update thin` will update `rack` even though it's _also_ a dependency of -`rack-perftools_profiler`. - -In short, by default, when you update a gem using `bundle update`, bundler will -update all dependencies of that gem, including those that are also dependencies -of another gem. - -To prevent updating shared dependencies, prior to version 1.14 the only option -was the `CONSERVATIVE UPDATING` behavior in [bundle install(1)](bundle-install.1.html): - -In this scenario, updating the `thin` version manually in the Gemfile(5), -and then running [bundle install(1)](bundle-install.1.html) will only update `daemons` and `eventmachine`, -but not `rack`. For more information, see the `CONSERVATIVE UPDATING` section -of [bundle install(1)](bundle-install.1.html). - -Starting with 1.14, specifying the `--conservative` option will also prevent shared -dependencies from being updated. - -## PATCH LEVEL OPTIONS - -Version 1.14 introduced 4 patch-level options that will influence how gem -versions are resolved. One of the following options can be used: `--patch`, -`--minor` or `--major`. `--strict` can be added to further influence resolution. - -* `--patch`: - Prefer updating only to next patch version. - -* `--minor`: - Prefer updating only to next minor version. - -* `--major`: - Prefer updating to next major version (default). - -* `--strict`: - Do not allow any gem to be updated past latest `--patch` | `--minor` | `--major`. - -When Bundler is resolving what versions to use to satisfy declared -requirements in the Gemfile or in parent gems, it looks up all -available versions, filters out any versions that don't satisfy -the requirement, and then, by default, sorts them from newest to -oldest, considering them in that order. - -Providing one of the patch level options (e.g. `--patch`) changes the -sort order of the satisfying versions, causing Bundler to consider the -latest `--patch` or `--minor` version available before other versions. -Note that versions outside the stated patch level could still be -resolved to if necessary to find a suitable dependency graph. - -For example, if gem 'foo' is locked at 1.0.2, with no gem requirement -defined in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0 -all exist, the default order of preference by default (`--major`) will -be "2.0.0, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2". - -If the `--patch` option is used, the order of preference will change to -"1.0.4, 1.0.3, 1.0.2, 1.1.1, 1.1.0, 2.0.0". - -If the `--minor` option is used, the order of preference will change to -"1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0". - -Combining the `--strict` option with any of the patch level options -will remove any versions beyond the scope of the patch level option, -to ensure that no gem is updated that far. - -To continue the previous example, if both `--patch` and `--strict` -options are used, the available versions for resolution would be -"1.0.4, 1.0.3, 1.0.2". If `--minor` and `--strict` are used, it would -be "1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2". - -Gem requirements as defined in the Gemfile will still be the first -determining factor for what versions are available. If the gem -requirement for `foo` in the Gemfile is '~> 1.0', that will accomplish -the same thing as providing the `--minor` and `--strict` options. - -## PATCH LEVEL EXAMPLES - -Given the following gem specifications: - - foo 1.4.3, requires: ~> bar 2.0 - foo 1.4.4, requires: ~> bar 2.0 - foo 1.4.5, requires: ~> bar 2.1 - foo 1.5.0, requires: ~> bar 2.1 - foo 1.5.1, requires: ~> bar 3.0 - bar with versions 2.0.3, 2.0.4, 2.1.0, 2.1.1, 3.0.0 - -Gemfile: - - gem 'foo' - -Gemfile.lock: - - foo (1.4.3) - bar (~> 2.0) - bar (2.0.3) - -Cases: - - # Command Line Result - ------------------------------------------------------------ - 1 bundle update --patch 'foo 1.4.5', 'bar 2.1.1' - 2 bundle update --patch foo 'foo 1.4.5', 'bar 2.1.1' - 3 bundle update --minor 'foo 1.5.1', 'bar 3.0.0' - 4 bundle update --minor --strict 'foo 1.5.0', 'bar 2.1.1' - 5 bundle update --patch --strict 'foo 1.4.4', 'bar 2.0.4' - -In case 1, bar is upgraded to 2.1.1, a minor version increase, because -the dependency from foo 1.4.5 required it. - -In case 2, only foo is requested to be unlocked, but bar is also -allowed to move because it's not a declared dependency in the Gemfile. - -In case 3, bar goes up a whole major release, because a minor increase -is preferred now for foo, and when it goes to 1.5.1, it requires 3.0.0 -of bar. - -In case 4, foo is preferred up to a minor version, but 1.5.1 won't work -because the --strict flag removes bar 3.0.0 from consideration since -it's a major increment. - -In case 5, both foo and bar have any minor or major increments removed -from consideration because of the --strict flag, so the most they can -move is up to 1.4.4 and 2.0.4. - -## RECOMMENDED WORKFLOW - -In general, when working with an application managed with bundler, you should -use the following workflow: - -* After you create your Gemfile(5) for the first time, run - - $ bundle install - -* Check the resulting `Gemfile.lock` into version control - - $ git add Gemfile.lock - -* When checking out this repository on another development machine, run - - $ bundle install - -* When checking out this repository on a deployment machine, run - - $ bundle install --deployment - -* After changing the Gemfile(5) to reflect a new or update dependency, run - - $ bundle install - -* Make sure to check the updated `Gemfile.lock` into version control - - $ git add Gemfile.lock - -* If [bundle install(1)](bundle-install.1.html) reports a conflict, manually update the specific - gems that you changed in the Gemfile(5) - - $ bundle update rails thin - -* If you want to update all the gems to the latest possible versions that - still match the gems listed in the Gemfile(5), run - - $ bundle update --all diff --git a/man/bundle-viz.1 b/man/bundle-viz.1 deleted file mode 100644 index cb2fcde537..0000000000 --- a/man/bundle-viz.1 +++ /dev/null @@ -1,39 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-VIZ" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile -. -.SH "SYNOPSIS" -\fBbundle viz\fR [\-\-file=FILE] [\-\-format=FORMAT] [\-\-requirements] [\-\-version] [\-\-without=GROUP GROUP] -. -.SH "DESCRIPTION" -\fBviz\fR generates a PNG file of the current \fBGemfile(5)\fR as a dependency graph\. \fBviz\fR requires the ruby\-graphviz gem (and its dependencies)\. -. -.P -The associated gems must also be installed via \fBbundle install(1)\fR \fIbundle\-install\.1\.html\fR\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-file\fR, \fB\-f\fR -The name to use for the generated file\. See \fB\-\-format\fR option -. -.TP -\fB\-\-format\fR, \fB\-F\fR -This is output format option\. Supported format is png, jpg, svg, dot \.\.\. -. -.TP -\fB\-\-requirements\fR, \fB\-R\fR -Set to show the version of each required dependency\. -. -.TP -\fB\-\-version\fR, \fB\-v\fR -Set to show each gem version\. -. -.TP -\fB\-\-without\fR, \fB\-W\fR -Exclude gems that are part of the specified named group\. - diff --git a/man/bundle-viz.1.ronn b/man/bundle-viz.1.ronn deleted file mode 100644 index 701df5415e..0000000000 --- a/man/bundle-viz.1.ronn +++ /dev/null @@ -1,30 +0,0 @@ -bundle-viz(1) -- Generates a visual dependency graph for your Gemfile -===================================================================== - -## SYNOPSIS - -`bundle viz` [--file=FILE] - [--format=FORMAT] - [--requirements] - [--version] - [--without=GROUP GROUP] - -## DESCRIPTION - -`viz` generates a PNG file of the current `Gemfile(5)` as a dependency graph. -`viz` requires the ruby-graphviz gem (and its dependencies). - -The associated gems must also be installed via [`bundle install(1)`](bundle-install.1.html). - -## OPTIONS - -* `--file`, `-f`: - The name to use for the generated file. See `--format` option -* `--format`, `-F`: - This is output format option. Supported format is png, jpg, svg, dot ... -* `--requirements`, `-R`: - Set to show the version of each required dependency. -* `--version`, `-v`: - Set to show each gem version. -* `--without`, `-W`: - Exclude gems that are part of the specified named group. diff --git a/man/bundle.1 b/man/bundle.1 deleted file mode 100644 index 86d0aec497..0000000000 --- a/man/bundle.1 +++ /dev/null @@ -1,136 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE" "1" "October 2020" "" "" -. -.SH "NAME" -\fBbundle\fR \- Ruby Dependency Management -. -.SH "SYNOPSIS" -\fBbundle\fR COMMAND [\-\-no\-color] [\-\-verbose] [ARGS] -. -.SH "DESCRIPTION" -Bundler manages an \fBapplication\'s dependencies\fR through its entire life across many machines systematically and repeatably\. -. -.P -See the bundler website \fIhttps://bundler\.io\fR for information on getting started, and Gemfile(5) for more information on the \fBGemfile\fR format\. -. -.SH "OPTIONS" -. -.TP -\fB\-\-no\-color\fR -Print all output without color -. -.TP -\fB\-\-retry\fR, \fB\-r\fR -Specify the number of times you wish to attempt network commands -. -.TP -\fB\-\-verbose\fR, \fB\-V\fR -Print out additional logging information -. -.SH "BUNDLE COMMANDS" -We divide \fBbundle\fR subcommands into primary commands and utilities: -. -.SH "PRIMARY COMMANDS" -. -.TP -\fBbundle install(1)\fR \fIbundle\-install\.1\.html\fR -Install the gems specified by the \fBGemfile\fR or \fBGemfile\.lock\fR -. -.TP -\fBbundle update(1)\fR \fIbundle\-update\.1\.html\fR -Update dependencies to their latest versions -. -.TP -\fBbundle package(1)\fR \fIbundle\-package\.1\.html\fR -Package the \.gem files required by your application into the \fBvendor/cache\fR directory -. -.TP -\fBbundle exec(1)\fR \fIbundle\-exec\.1\.html\fR -Execute a script in the current bundle -. -.TP -\fBbundle config(1)\fR \fIbundle\-config\.1\.html\fR -Specify and read configuration options for Bundler -. -.TP -\fBbundle help(1)\fR -Display detailed help for each subcommand -. -.SH "UTILITIES" -. -.TP -\fBbundle add(1)\fR \fIbundle\-add\.1\.html\fR -Add the named gem to the Gemfile and run \fBbundle install\fR -. -.TP -\fBbundle binstubs(1)\fR \fIbundle\-binstubs\.1\.html\fR -Generate binstubs for executables in a gem -. -.TP -\fBbundle check(1)\fR \fIbundle\-check\.1\.html\fR -Determine whether the requirements for your application are installed and available to Bundler -. -.TP -\fBbundle show(1)\fR \fIbundle\-show\.1\.html\fR -Show the source location of a particular gem in the bundle -. -.TP -\fBbundle outdated(1)\fR \fIbundle\-outdated\.1\.html\fR -Show all of the outdated gems in the current bundle -. -.TP -\fBbundle console(1)\fR -Start an IRB session in the current bundle -. -.TP -\fBbundle open(1)\fR \fIbundle\-open\.1\.html\fR -Open an installed gem in the editor -. -.TP -\fBbundle lock(1)\fR \fIbundle\-lock\.1\.html\fR -Generate a lockfile for your dependencies -. -.TP -\fBbundle viz(1)\fR \fIbundle\-viz\.1\.html\fR -Generate a visual representation of your dependencies -. -.TP -\fBbundle init(1)\fR \fIbundle\-init\.1\.html\fR -Generate a simple \fBGemfile\fR, placed in the current directory -. -.TP -\fBbundle gem(1)\fR \fIbundle\-gem\.1\.html\fR -Create a simple gem, suitable for development with Bundler -. -.TP -\fBbundle platform(1)\fR \fIbundle\-platform\.1\.html\fR -Display platform compatibility information -. -.TP -\fBbundle clean(1)\fR \fIbundle\-clean\.1\.html\fR -Clean up unused gems in your Bundler directory -. -.TP -\fBbundle doctor(1)\fR \fIbundle\-doctor\.1\.html\fR -Display warnings about common problems -. -.TP -\fBbundle remove(1)\fR \fIbundle\-remove\.1\.html\fR -Removes gems from the Gemfile -. -.SH "PLUGINS" -When running a command that isn\'t listed in PRIMARY COMMANDS or UTILITIES, Bundler will try to find an executable on your path named \fBbundler\-<command>\fR and execute it, passing down any extra arguments to it\. -. -.SH "OBSOLETE" -These commands are obsolete and should no longer be used: -. -.IP "\(bu" 4 -\fBbundle cache(1)\fR -. -.IP "\(bu" 4 -\fBbundle show(1)\fR -. -.IP "" 0 - diff --git a/man/bundle.1.ronn b/man/bundle.1.ronn deleted file mode 100644 index 5b1712394a..0000000000 --- a/man/bundle.1.ronn +++ /dev/null @@ -1,111 +0,0 @@ -bundle(1) -- Ruby Dependency Management -======================================= - -## SYNOPSIS - -`bundle` COMMAND [--no-color] [--verbose] [ARGS] - -## DESCRIPTION - -Bundler manages an `application's dependencies` through its entire life -across many machines systematically and repeatably. - -See [the bundler website](https://bundler.io) for information on getting -started, and Gemfile(5) for more information on the `Gemfile` format. - -## OPTIONS - -* `--no-color`: - Print all output without color - -* `--retry`, `-r`: - Specify the number of times you wish to attempt network commands - -* `--verbose`, `-V`: - Print out additional logging information - -## BUNDLE COMMANDS - -We divide `bundle` subcommands into primary commands and utilities: - -## PRIMARY COMMANDS - -* [`bundle install(1)`](bundle-install.1.html): - Install the gems specified by the `Gemfile` or `Gemfile.lock` - -* [`bundle update(1)`](bundle-update.1.html): - Update dependencies to their latest versions - -* [`bundle package(1)`](bundle-package.1.html): - Package the .gem files required by your application into the - `vendor/cache` directory - -* [`bundle exec(1)`](bundle-exec.1.html): - Execute a script in the current bundle - -* [`bundle config(1)`](bundle-config.1.html): - Specify and read configuration options for Bundler - -* `bundle help(1)`: - Display detailed help for each subcommand - -## UTILITIES - -* [`bundle add(1)`](bundle-add.1.html): - Add the named gem to the Gemfile and run `bundle install` - -* [`bundle binstubs(1)`](bundle-binstubs.1.html): - Generate binstubs for executables in a gem - -* [`bundle check(1)`](bundle-check.1.html): - Determine whether the requirements for your application are installed - and available to Bundler - -* [`bundle show(1)`](bundle-show.1.html): - Show the source location of a particular gem in the bundle - -* [`bundle outdated(1)`](bundle-outdated.1.html): - Show all of the outdated gems in the current bundle - -* `bundle console(1)`: - Start an IRB session in the current bundle - -* [`bundle open(1)`](bundle-open.1.html): - Open an installed gem in the editor - -* [`bundle lock(1)`](bundle-lock.1.html): - Generate a lockfile for your dependencies - -* [`bundle viz(1)`](bundle-viz.1.html): - Generate a visual representation of your dependencies - -* [`bundle init(1)`](bundle-init.1.html): - Generate a simple `Gemfile`, placed in the current directory - -* [`bundle gem(1)`](bundle-gem.1.html): - Create a simple gem, suitable for development with Bundler - -* [`bundle platform(1)`](bundle-platform.1.html): - Display platform compatibility information - -* [`bundle clean(1)`](bundle-clean.1.html): - Clean up unused gems in your Bundler directory - -* [`bundle doctor(1)`](bundle-doctor.1.html): - Display warnings about common problems - -* [`bundle remove(1)`](bundle-remove.1.html): - Removes gems from the Gemfile - -## PLUGINS - -When running a command that isn't listed in PRIMARY COMMANDS or UTILITIES, -Bundler will try to find an executable on your path named `bundler-<command>` -and execute it, passing down any extra arguments to it. - -## OBSOLETE - -These commands are obsolete and should no longer be used: - -* `bundle cache(1)` -* `bundle show(1)` @@ -1,6 +1,6 @@ .\"Ruby is copyrighted by Yukihiro Matsumoto <matz@netlab.jp>. -.Dd December 16, 2018 -.Dt ERB \&1 "Ruby Programmer's Reference Guide" +.Dd March 27, 2026 +.Dt ERB 1 "Ruby Programmer's Reference Guide" .Os UNIX .Sh NAME .Nm erb diff --git a/man/gemfile.5 b/man/gemfile.5 deleted file mode 100644 index 401487c688..0000000000 --- a/man/gemfile.5 +++ /dev/null @@ -1,686 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "GEMFILE" "5" "October 2020" "" "" -. -.SH "NAME" -\fBGemfile\fR \- A format for describing gem dependencies for Ruby programs -. -.SH "SYNOPSIS" -A \fBGemfile\fR describes the gem dependencies required to execute associated Ruby code\. -. -.P -Place the \fBGemfile\fR in the root of the directory containing the associated code\. For instance, in a Rails application, place the \fBGemfile\fR in the same directory as the \fBRakefile\fR\. -. -.SH "SYNTAX" -A \fBGemfile\fR is evaluated as Ruby code, in a context which makes available a number of methods used to describe the gem requirements\. -. -.SH "GLOBAL SOURCES" -At the top of the \fBGemfile\fR, add a line for the \fBRubygems\fR source that contains the gems listed in the \fBGemfile\fR\. -. -.IP "" 4 -. -.nf - -source "https://rubygems\.org" -. -.fi -. -.IP "" 0 -. -.P -It is possible, but not recommended as of Bundler 1\.7, to add multiple global \fBsource\fR lines\. Each of these \fBsource\fRs \fBMUST\fR be a valid Rubygems repository\. -. -.P -Sources are checked for gems following the heuristics described in \fISOURCE PRIORITY\fR\. If a gem is found in more than one global source, Bundler will print a warning after installing the gem indicating which source was used, and listing the other sources where the gem is available\. A specific source can be selected for gems that need to use a non\-standard repository, suppressing this warning, by using the \fI\fB:source\fR option\fR or a \fI\fBsource\fR block\fR\. -. -.SS "CREDENTIALS" -Some gem sources require a username and password\. Use bundle config(1) \fIbundle\-config\.1\.html\fR to set the username and password for any of the sources that need it\. The command must be run once on each computer that will install the Gemfile, but this keeps the credentials from being stored in plain text in version control\. -. -.IP "" 4 -. -.nf - -bundle config gems\.example\.com user:password -. -.fi -. -.IP "" 0 -. -.P -For some sources, like a company Gemfury account, it may be easier to include the credentials in the Gemfile as part of the source URL\. -. -.IP "" 4 -. -.nf - -source "https://user:password@gems\.example\.com" -. -.fi -. -.IP "" 0 -. -.P -Credentials in the source URL will take precedence over credentials set using \fBconfig\fR\. -. -.SH "RUBY" -If your application requires a specific Ruby version or engine, specify your requirements using the \fBruby\fR method, with the following arguments\. All parameters are \fBOPTIONAL\fR unless otherwise specified\. -. -.SS "VERSION (required)" -The version of Ruby that your application requires\. If your application requires an alternate Ruby engine, such as JRuby, Rubinius or TruffleRuby, this should be the Ruby version that the engine is compatible with\. -. -.IP "" 4 -. -.nf - -ruby "1\.9\.3" -. -.fi -. -.IP "" 0 -. -.SS "ENGINE" -Each application \fImay\fR specify a Ruby engine\. If an engine is specified, an engine version \fImust\fR also be specified\. -. -.P -What exactly is an Engine? \- A Ruby engine is an implementation of the Ruby language\. -. -.IP "\(bu" 4 -For background: the reference or original implementation of the Ruby programming language is called Matz\'s Ruby Interpreter \fIhttps://en\.wikipedia\.org/wiki/Ruby_MRI\fR, or MRI for short\. This is named after Ruby creator Yukihiro Matsumoto, also known as Matz\. MRI is also known as CRuby, because it is written in C\. MRI is the most widely used Ruby engine\. -. -.IP "\(bu" 4 -Other implementations \fIhttps://www\.ruby\-lang\.org/en/about/\fR of Ruby exist\. Some of the more well\-known implementations include Rubinius \fIhttps://rubinius\.com/\fR, and JRuby \fIhttp://jruby\.org/\fR\. Rubinius is an alternative implementation of Ruby written in Ruby\. JRuby is an implementation of Ruby on the JVM, short for Java Virtual Machine\. -. -.IP "" 0 -. -.SS "ENGINE VERSION" -Each application \fImay\fR specify a Ruby engine version\. If an engine version is specified, an engine \fImust\fR also be specified\. If the engine is "ruby" the engine version specified \fImust\fR match the Ruby version\. -. -.IP "" 4 -. -.nf - -ruby "1\.8\.7", :engine => "jruby", :engine_version => "1\.6\.7" -. -.fi -. -.IP "" 0 -. -.SS "PATCHLEVEL" -Each application \fImay\fR specify a Ruby patchlevel\. -. -.IP "" 4 -. -.nf - -ruby "2\.0\.0", :patchlevel => "247" -. -.fi -. -.IP "" 0 -. -.SH "GEMS" -Specify gem requirements using the \fBgem\fR method, with the following arguments\. All parameters are \fBOPTIONAL\fR unless otherwise specified\. -. -.SS "NAME (required)" -For each gem requirement, list a single \fIgem\fR line\. -. -.IP "" 4 -. -.nf - -gem "nokogiri" -. -.fi -. -.IP "" 0 -. -.SS "VERSION" -Each \fIgem\fR \fBMAY\fR have one or more version specifiers\. -. -.IP "" 4 -. -.nf - -gem "nokogiri", ">= 1\.4\.2" -gem "RedCloth", ">= 4\.1\.0", "< 4\.2\.0" -. -.fi -. -.IP "" 0 -. -.SS "REQUIRE AS" -Each \fIgem\fR \fBMAY\fR specify files that should be used when autorequiring via \fBBundler\.require\fR\. You may pass an array with multiple files or \fBtrue\fR if the file you want \fBrequired\fR has the same name as \fIgem\fR or \fBfalse\fR to prevent any file from being autorequired\. -. -.IP "" 4 -. -.nf - -gem "redis", :require => ["redis/connection/hiredis", "redis"] -gem "webmock", :require => false -gem "byebug", :require => true -. -.fi -. -.IP "" 0 -. -.P -The argument defaults to the name of the gem\. For example, these are identical: -. -.IP "" 4 -. -.nf - -gem "nokogiri" -gem "nokogiri", :require => "nokogiri" -gem "nokogiri", :require => true -. -.fi -. -.IP "" 0 -. -.SS "GROUPS" -Each \fIgem\fR \fBMAY\fR specify membership in one or more groups\. Any \fIgem\fR that does not specify membership in any group is placed in the \fBdefault\fR group\. -. -.IP "" 4 -. -.nf - -gem "rspec", :group => :test -gem "wirble", :groups => [:development, :test] -. -.fi -. -.IP "" 0 -. -.P -The Bundler runtime allows its two main methods, \fBBundler\.setup\fR and \fBBundler\.require\fR, to limit their impact to particular groups\. -. -.IP "" 4 -. -.nf - -# setup adds gems to Ruby\'s load path -Bundler\.setup # defaults to all groups -require "bundler/setup" # same as Bundler\.setup -Bundler\.setup(:default) # only set up the _default_ group -Bundler\.setup(:test) # only set up the _test_ group (but `not` _default_) -Bundler\.setup(:default, :test) # set up the _default_ and _test_ groups, but no others - -# require requires all of the gems in the specified groups -Bundler\.require # defaults to the _default_ group -Bundler\.require(:default) # identical -Bundler\.require(:default, :test) # requires the _default_ and _test_ groups -Bundler\.require(:test) # requires the _test_ group -. -.fi -. -.IP "" 0 -. -.P -The Bundler CLI allows you to specify a list of groups whose gems \fBbundle install\fR should not install with the \fBwithout\fR configuration\. -. -.P -To specify multiple groups to ignore, specify a list of groups separated by spaces\. -. -.IP "" 4 -. -.nf - -bundle config set \-\-local without test -bundle config set \-\-local without development test -. -.fi -. -.IP "" 0 -. -.P -Also, calling \fBBundler\.setup\fR with no parameters, or calling \fBrequire "bundler/setup"\fR will setup all groups except for the ones you excluded via \fB\-\-without\fR (since they are not available)\. -. -.P -Note that on \fBbundle install\fR, bundler downloads and evaluates all gems, in order to create a single canonical list of all of the required gems and their dependencies\. This means that you cannot list different versions of the same gems in different groups\. For more details, see Understanding Bundler \fIhttps://bundler\.io/rationale\.html\fR\. -. -.SS "PLATFORMS" -If a gem should only be used in a particular platform or set of platforms, you can specify them\. Platforms are essentially identical to groups, except that you do not need to use the \fB\-\-without\fR install\-time flag to exclude groups of gems for other platforms\. -. -.P -There are a number of \fBGemfile\fR platforms: -. -.TP -\fBruby\fR -C Ruby (MRI), Rubinius or TruffleRuby, but \fBNOT\fR Windows -. -.TP -\fBmri\fR -Same as \fIruby\fR, but only C Ruby (MRI) -. -.TP -\fBmingw\fR -Windows 32 bit \'mingw32\' platform (aka RubyInstaller) -. -.TP -\fBx64_mingw\fR -Windows 64 bit \'mingw32\' platform (aka RubyInstaller x64) -. -.TP -\fBrbx\fR -Rubinius -. -.TP -\fBjruby\fR -JRuby -. -.TP -\fBtruffleruby\fR -TruffleRuby -. -.TP -\fBmswin\fR -Windows -. -.P -You can restrict further by platform and version for all platforms \fIexcept\fR for \fBrbx\fR, \fBjruby\fR, \fBtruffleruby\fR and \fBmswin\fR\. -. -.P -To specify a version in addition to a platform, append the version number without the delimiter to the platform\. For example, to specify that a gem should only be used on platforms with Ruby 2\.3, use: -. -.IP "" 4 -. -.nf - -ruby_23 -. -.fi -. -.IP "" 0 -. -.P -The full list of platforms and supported versions includes: -. -.TP -\fBruby\fR -1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6 -. -.TP -\fBmri\fR -1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6 -. -.TP -\fBmingw\fR -1\.8, 1\.9, 2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6 -. -.TP -\fBx64_mingw\fR -2\.0, 2\.1, 2\.2, 2\.3, 2\.4, 2\.5, 2\.6 -. -.P -As with groups, you can specify one or more platforms: -. -.IP "" 4 -. -.nf - -gem "weakling", :platforms => :jruby -gem "ruby\-debug", :platforms => :mri_18 -gem "nokogiri", :platforms => [:mri_18, :jruby] -. -.fi -. -.IP "" 0 -. -.P -All operations involving groups (\fBbundle install\fR \fIbundle\-install\.1\.html\fR, \fBBundler\.setup\fR, \fBBundler\.require\fR) behave exactly the same as if any groups not matching the current platform were explicitly excluded\. -. -.SS "SOURCE" -You can select an alternate Rubygems repository for a gem using the \':source\' option\. -. -.IP "" 4 -. -.nf - -gem "some_internal_gem", :source => "https://gems\.example\.com" -. -.fi -. -.IP "" 0 -. -.P -This forces the gem to be loaded from this source and ignores any global sources declared at the top level of the file\. If the gem does not exist in this source, it will not be installed\. -. -.P -Bundler will search for child dependencies of this gem by first looking in the source selected for the parent, but if they are not found there, it will fall back on global sources using the ordering described in \fISOURCE PRIORITY\fR\. -. -.P -Selecting a specific source repository this way also suppresses the ambiguous gem warning described above in \fIGLOBAL SOURCES (#source)\fR\. -. -.P -Using the \fB:source\fR option for an individual gem will also make that source available as a possible global source for any other gems which do not specify explicit sources\. Thus, when adding gems with explicit sources, it is recommended that you also ensure all other gems in the Gemfile are using explicit sources\. -. -.SS "GIT" -If necessary, you can specify that a gem is located at a particular git repository using the \fB:git\fR parameter\. The repository can be accessed via several protocols: -. -.TP -\fBHTTP(S)\fR -gem "rails", :git => "https://github\.com/rails/rails\.git" -. -.TP -\fBSSH\fR -gem "rails", :git => "git@github\.com:rails/rails\.git" -. -.TP -\fBgit\fR -gem "rails", :git => "git://github\.com/rails/rails\.git" -. -.P -If using SSH, the user that you use to run \fBbundle install\fR \fBMUST\fR have the appropriate keys available in their \fB$HOME/\.ssh\fR\. -. -.P -\fBNOTE\fR: \fBhttp://\fR and \fBgit://\fR URLs should be avoided if at all possible\. These protocols are unauthenticated, so a man\-in\-the\-middle attacker can deliver malicious code and compromise your system\. HTTPS and SSH are strongly preferred\. -. -.P -The \fBgroup\fR, \fBplatforms\fR, and \fBrequire\fR options are available and behave exactly the same as they would for a normal gem\. -. -.P -A git repository \fBSHOULD\fR have at least one file, at the root of the directory containing the gem, with the extension \fB\.gemspec\fR\. This file \fBMUST\fR contain a valid gem specification, as expected by the \fBgem build\fR command\. -. -.P -If a git repository does not have a \fB\.gemspec\fR, bundler will attempt to create one, but it will not contain any dependencies, executables, or C extension compilation instructions\. As a result, it may fail to properly integrate into your application\. -. -.P -If a git repository does have a \fB\.gemspec\fR for the gem you attached it to, a version specifier, if provided, means that the git repository is only valid if the \fB\.gemspec\fR specifies a version matching the version specifier\. If not, bundler will print a warning\. -. -.IP "" 4 -. -.nf - -gem "rails", "2\.3\.8", :git => "https://github\.com/rails/rails\.git" -# bundle install will fail, because the \.gemspec in the rails -# repository\'s master branch specifies version 3\.0\.0 -. -.fi -. -.IP "" 0 -. -.P -If a git repository does \fBnot\fR have a \fB\.gemspec\fR for the gem you attached it to, a version specifier \fBMUST\fR be provided\. Bundler will use this version in the simple \fB\.gemspec\fR it creates\. -. -.P -Git repositories support a number of additional options\. -. -.TP -\fBbranch\fR, \fBtag\fR, and \fBref\fR -You \fBMUST\fR only specify at most one of these options\. The default is \fB:branch => "master"\fR\. For example: -. -.IP -gem "rails", :git => "https://github\.com/rails/rails\.git", :branch => "5\-0\-stable" -. -.IP -gem "rails", :git => "https://github\.com/rails/rails\.git", :tag => "v5\.0\.0" -. -.IP -gem "rails", :git => "https://github\.com/rails/rails\.git", :ref => "4aded" -. -.TP -\fBsubmodules\fR -For reference, a git submodule \fIhttps://git\-scm\.com/book/en/v2/Git\-Tools\-Submodules\fR lets you have another git repository within a subfolder of your repository\. Specify \fB:submodules => true\fR to cause bundler to expand any submodules included in the git repository -. -.P -If a git repository contains multiple \fB\.gemspecs\fR, each \fB\.gemspec\fR represents a gem located at the same place in the file system as the \fB\.gemspec\fR\. -. -.IP "" 4 -. -.nf - -|~rails [git root] -| |\-rails\.gemspec [rails gem located here] -|~actionpack -| |\-actionpack\.gemspec [actionpack gem located here] -|~activesupport -| |\-activesupport\.gemspec [activesupport gem located here] -|\.\.\. -. -.fi -. -.IP "" 0 -. -.P -To install a gem located in a git repository, bundler changes to the directory containing the gemspec, runs \fBgem build name\.gemspec\fR and then installs the resulting gem\. The \fBgem build\fR command, which comes standard with Rubygems, evaluates the \fB\.gemspec\fR in the context of the directory in which it is located\. -. -.SS "GIT SOURCE" -A custom git source can be defined via the \fBgit_source\fR method\. Provide the source\'s name as an argument, and a block which receives a single argument and interpolates it into a string to return the full repo address: -. -.IP "" 4 -. -.nf - -git_source(:stash){ |repo_name| "https://stash\.corp\.acme\.pl/#{repo_name}\.git" } -gem \'rails\', :stash => \'forks/rails\' -. -.fi -. -.IP "" 0 -. -.P -In addition, if you wish to choose a specific branch: -. -.IP "" 4 -. -.nf - -gem "rails", :stash => "forks/rails", :branch => "branch_name" -. -.fi -. -.IP "" 0 -. -.SS "GITHUB" -\fBNOTE\fR: This shorthand should be avoided until Bundler 2\.0, since it currently expands to an insecure \fBgit://\fR URL\. This allows a man\-in\-the\-middle attacker to compromise your system\. -. -.P -If the git repository you want to use is hosted on GitHub and is public, you can use the :github shorthand to specify the github username and repository name (without the trailing "\.git"), separated by a slash\. If both the username and repository name are the same, you can omit one\. -. -.IP "" 4 -. -.nf - -gem "rails", :github => "rails/rails" -gem "rails", :github => "rails" -. -.fi -. -.IP "" 0 -. -.P -Are both equivalent to -. -.IP "" 4 -. -.nf - -gem "rails", :git => "git://github\.com/rails/rails\.git" -. -.fi -. -.IP "" 0 -. -.P -Since the \fBgithub\fR method is a specialization of \fBgit_source\fR, it accepts a \fB:branch\fR named argument\. -. -.SS "GIST" -If the git repository you want to use is hosted as a Github Gist and is public, you can use the :gist shorthand to specify the gist identifier (without the trailing "\.git")\. -. -.IP "" 4 -. -.nf - -gem "the_hatch", :gist => "4815162342" -. -.fi -. -.IP "" 0 -. -.P -Is equivalent to: -. -.IP "" 4 -. -.nf - -gem "the_hatch", :git => "https://gist\.github\.com/4815162342\.git" -. -.fi -. -.IP "" 0 -. -.P -Since the \fBgist\fR method is a specialization of \fBgit_source\fR, it accepts a \fB:branch\fR named argument\. -. -.SS "BITBUCKET" -If the git repository you want to use is hosted on Bitbucket and is public, you can use the :bitbucket shorthand to specify the bitbucket username and repository name (without the trailing "\.git"), separated by a slash\. If both the username and repository name are the same, you can omit one\. -. -.IP "" 4 -. -.nf - -gem "rails", :bitbucket => "rails/rails" -gem "rails", :bitbucket => "rails" -. -.fi -. -.IP "" 0 -. -.P -Are both equivalent to -. -.IP "" 4 -. -.nf - -gem "rails", :git => "https://rails@bitbucket\.org/rails/rails\.git" -. -.fi -. -.IP "" 0 -. -.P -Since the \fBbitbucket\fR method is a specialization of \fBgit_source\fR, it accepts a \fB:branch\fR named argument\. -. -.SS "PATH" -You can specify that a gem is located in a particular location on the file system\. Relative paths are resolved relative to the directory containing the \fBGemfile\fR\. -. -.P -Similar to the semantics of the \fB:git\fR option, the \fB:path\fR option requires that the directory in question either contains a \fB\.gemspec\fR for the gem, or that you specify an explicit version that bundler should use\. -. -.P -Unlike \fB:git\fR, bundler does not compile C extensions for gems specified as paths\. -. -.IP "" 4 -. -.nf - -gem "rails", :path => "vendor/rails" -. -.fi -. -.IP "" 0 -. -.P -If you would like to use multiple local gems directly from the filesystem, you can set a global \fBpath\fR option to the path containing the gem\'s files\. This will automatically load gemspec files from subdirectories\. -. -.IP "" 4 -. -.nf - -path \'components\' do - gem \'admin_ui\' - gem \'public_ui\' -end -. -.fi -. -.IP "" 0 -. -.SH "BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS" -The \fB:source\fR, \fB:git\fR, \fB:path\fR, \fB:group\fR, and \fB:platforms\fR options may be applied to a group of gems by using block form\. -. -.IP "" 4 -. -.nf - -source "https://gems\.example\.com" do - gem "some_internal_gem" - gem "another_internal_gem" -end - -git "https://github\.com/rails/rails\.git" do - gem "activesupport" - gem "actionpack" -end - -platforms :ruby do - gem "ruby\-debug" - gem "sqlite3" -end - -group :development, :optional => true do - gem "wirble" - gem "faker" -end -. -.fi -. -.IP "" 0 -. -.P -In the case of the group block form the :optional option can be given to prevent a group from being installed unless listed in the \fB\-\-with\fR option given to the \fBbundle install\fR command\. -. -.P -In the case of the \fBgit\fR block form, the \fB:ref\fR, \fB:branch\fR, \fB:tag\fR, and \fB:submodules\fR options may be passed to the \fBgit\fR method, and all gems in the block will inherit those options\. -. -.P -The presence of a \fBsource\fR block in a Gemfile also makes that source available as a possible global source for any other gems which do not specify explicit sources\. Thus, when defining source blocks, it is recommended that you also ensure all other gems in the Gemfile are using explicit sources, either via source blocks or \fB:source\fR directives on individual gems\. -. -.SH "INSTALL_IF" -The \fBinstall_if\fR method allows gems to be installed based on a proc or lambda\. This is especially useful for optional gems that can only be used if certain software is installed or some other conditions are met\. -. -.IP "" 4 -. -.nf - -install_if \-> { RUBY_PLATFORM =~ /darwin/ } do - gem "pasteboard" -end -. -.fi -. -.IP "" 0 -. -.SH "GEMSPEC" -The \fB\.gemspec\fR \fIhttp://guides\.rubygems\.org/specification\-reference/\fR file is where you provide metadata about your gem to Rubygems\. Some required Gemspec attributes include the name, description, and homepage of your gem\. This is also where you specify the dependencies your gem needs to run\. -. -.P -If you wish to use Bundler to help install dependencies for a gem while it is being developed, use the \fBgemspec\fR method to pull in the dependencies listed in the \fB\.gemspec\fR file\. -. -.P -The \fBgemspec\fR method adds any runtime dependencies as gem requirements in the default group\. It also adds development dependencies as gem requirements in the \fBdevelopment\fR group\. Finally, it adds a gem requirement on your project (\fB:path => \'\.\'\fR)\. In conjunction with \fBBundler\.setup\fR, this allows you to require project files in your test code as you would if the project were installed as a gem; you need not manipulate the load path manually or require project files via relative paths\. -. -.P -The \fBgemspec\fR method supports optional \fB:path\fR, \fB:glob\fR, \fB:name\fR, and \fB:development_group\fR options, which control where bundler looks for the \fB\.gemspec\fR, the glob it uses to look for the gemspec (defaults to: "{,\fI,\fR/*}\.gemspec"), what named \fB\.gemspec\fR it uses (if more than one is present), and which group development dependencies are included in\. -. -.P -When a \fBgemspec\fR dependency encounters version conflicts during resolution, the local version under development will always be selected \-\- even if there are remote versions that better match other requirements for the \fBgemspec\fR gem\. -. -.SH "SOURCE PRIORITY" -When attempting to locate a gem to satisfy a gem requirement, bundler uses the following priority order: -. -.IP "1." 4 -The source explicitly attached to the gem (using \fB:source\fR, \fB:path\fR, or \fB:git\fR) -. -.IP "2." 4 -For implicit gems (dependencies of explicit gems), any source, git, or path repository declared on the parent\. This results in bundler prioritizing the ActiveSupport gem from the Rails git repository over ones from \fBrubygems\.org\fR -. -.IP "3." 4 -The sources specified via global \fBsource\fR lines, searching each source in your \fBGemfile\fR from last added to first added\. -. -.IP "" 0 - diff --git a/man/gemfile.5.ronn b/man/gemfile.5.ronn deleted file mode 100644 index 994f0d66bd..0000000000 --- a/man/gemfile.5.ronn +++ /dev/null @@ -1,517 +0,0 @@ -Gemfile(5) -- A format for describing gem dependencies for Ruby programs -======================================================================== - -## SYNOPSIS - -A `Gemfile` describes the gem dependencies required to execute associated -Ruby code. - -Place the `Gemfile` in the root of the directory containing the associated -code. For instance, in a Rails application, place the `Gemfile` in the same -directory as the `Rakefile`. - -## SYNTAX - -A `Gemfile` is evaluated as Ruby code, in a context which makes available -a number of methods used to describe the gem requirements. - -## GLOBAL SOURCES - -At the top of the `Gemfile`, add a line for the `Rubygems` source that contains -the gems listed in the `Gemfile`. - - source "https://rubygems.org" - -It is possible, but not recommended as of Bundler 1.7, to add multiple global -`source` lines. Each of these `source`s `MUST` be a valid Rubygems repository. - -Sources are checked for gems following the heuristics described in -[SOURCE PRIORITY][]. If a gem is found in more than one global source, Bundler -will print a warning after installing the gem indicating which source was used, -and listing the other sources where the gem is available. A specific source can -be selected for gems that need to use a non-standard repository, suppressing -this warning, by using the [`:source` option](#SOURCE) or a -[`source` block](#BLOCK-FORM-OF-SOURCE-GIT-PATH-GROUP-and-PLATFORMS). - -### CREDENTIALS - -Some gem sources require a username and password. Use [bundle config(1)](bundle-config.1.html) to set -the username and password for any of the sources that need it. The command must -be run once on each computer that will install the Gemfile, but this keeps the -credentials from being stored in plain text in version control. - - bundle config gems.example.com user:password - -For some sources, like a company Gemfury account, it may be easier to -include the credentials in the Gemfile as part of the source URL. - - source "https://user:password@gems.example.com" - -Credentials in the source URL will take precedence over credentials set using -`config`. - -## RUBY - -If your application requires a specific Ruby version or engine, specify your -requirements using the `ruby` method, with the following arguments. -All parameters are `OPTIONAL` unless otherwise specified. - -### VERSION (required) - -The version of Ruby that your application requires. If your application -requires an alternate Ruby engine, such as JRuby, Rubinius or TruffleRuby, this -should be the Ruby version that the engine is compatible with. - - ruby "1.9.3" - -### ENGINE - -Each application _may_ specify a Ruby engine. If an engine is specified, an -engine version _must_ also be specified. - -What exactly is an Engine? - - A Ruby engine is an implementation of the Ruby language. - - - For background: the reference or original implementation of the Ruby - programming language is called - [Matz's Ruby Interpreter](https://en.wikipedia.org/wiki/Ruby_MRI), or MRI - for short. This is named after Ruby creator Yukihiro Matsumoto, - also known as Matz. MRI is also known as CRuby, because it is written in C. - MRI is the most widely used Ruby engine. - - - [Other implementations](https://www.ruby-lang.org/en/about/) of Ruby exist. - Some of the more well-known implementations include - [Rubinius](https://rubinius.com/), and [JRuby](http://jruby.org/). - Rubinius is an alternative implementation of Ruby written in Ruby. - JRuby is an implementation of Ruby on the JVM, short for Java Virtual Machine. - -### ENGINE VERSION - -Each application _may_ specify a Ruby engine version. If an engine version is -specified, an engine _must_ also be specified. If the engine is "ruby" the -engine version specified _must_ match the Ruby version. - - ruby "1.8.7", :engine => "jruby", :engine_version => "1.6.7" - -### PATCHLEVEL - -Each application _may_ specify a Ruby patchlevel. - - ruby "2.0.0", :patchlevel => "247" - -## GEMS - -Specify gem requirements using the `gem` method, with the following arguments. -All parameters are `OPTIONAL` unless otherwise specified. - -### NAME (required) - -For each gem requirement, list a single _gem_ line. - - gem "nokogiri" - -### VERSION - -Each _gem_ `MAY` have one or more version specifiers. - - gem "nokogiri", ">= 1.4.2" - gem "RedCloth", ">= 4.1.0", "< 4.2.0" - -### REQUIRE AS - -Each _gem_ `MAY` specify files that should be used when autorequiring via -`Bundler.require`. You may pass an array with multiple files or `true` if the file -you want `required` has the same name as _gem_ or `false` to -prevent any file from being autorequired. - - gem "redis", :require => ["redis/connection/hiredis", "redis"] - gem "webmock", :require => false - gem "byebug", :require => true - -The argument defaults to the name of the gem. For example, these are identical: - - gem "nokogiri" - gem "nokogiri", :require => "nokogiri" - gem "nokogiri", :require => true - -### GROUPS - -Each _gem_ `MAY` specify membership in one or more groups. Any _gem_ that does -not specify membership in any group is placed in the `default` group. - - gem "rspec", :group => :test - gem "wirble", :groups => [:development, :test] - -The Bundler runtime allows its two main methods, `Bundler.setup` and -`Bundler.require`, to limit their impact to particular groups. - - # setup adds gems to Ruby's load path - Bundler.setup # defaults to all groups - require "bundler/setup" # same as Bundler.setup - Bundler.setup(:default) # only set up the _default_ group - Bundler.setup(:test) # only set up the _test_ group (but `not` _default_) - Bundler.setup(:default, :test) # set up the _default_ and _test_ groups, but no others - - # require requires all of the gems in the specified groups - Bundler.require # defaults to the _default_ group - Bundler.require(:default) # identical - Bundler.require(:default, :test) # requires the _default_ and _test_ groups - Bundler.require(:test) # requires the _test_ group - -The Bundler CLI allows you to specify a list of groups whose gems `bundle install` should -not install with the `without` configuration. - -To specify multiple groups to ignore, specify a list of groups separated by spaces. - - bundle config set --local without test - bundle config set --local without development test - -Also, calling `Bundler.setup` with no parameters, or calling `require "bundler/setup"` -will setup all groups except for the ones you excluded via `--without` (since they -are not available). - -Note that on `bundle install`, bundler downloads and evaluates all gems, in order to -create a single canonical list of all of the required gems and their dependencies. -This means that you cannot list different versions of the same gems in different -groups. For more details, see [Understanding Bundler](https://bundler.io/rationale.html). - -### PLATFORMS - -If a gem should only be used in a particular platform or set of platforms, you can -specify them. Platforms are essentially identical to groups, except that you do not -need to use the `--without` install-time flag to exclude groups of gems for other -platforms. - -There are a number of `Gemfile` platforms: - - * `ruby`: - C Ruby (MRI), Rubinius or TruffleRuby, but `NOT` Windows - * `mri`: - Same as _ruby_, but only C Ruby (MRI) - * `mingw`: - Windows 32 bit 'mingw32' platform (aka RubyInstaller) - * `x64_mingw`: - Windows 64 bit 'mingw32' platform (aka RubyInstaller x64) - * `rbx`: - Rubinius - * `jruby`: - JRuby - * `truffleruby`: - TruffleRuby - * `mswin`: - Windows - -You can restrict further by platform and version for all platforms *except* for -`rbx`, `jruby`, `truffleruby` and `mswin`. - -To specify a version in addition to a platform, append the version number without -the delimiter to the platform. For example, to specify that a gem should only be -used on platforms with Ruby 2.3, use: - - ruby_23 - -The full list of platforms and supported versions includes: - - * `ruby`: - 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 - * `mri`: - 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 - * `mingw`: - 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 - * `x64_mingw`: - 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 - -As with groups, you can specify one or more platforms: - - gem "weakling", :platforms => :jruby - gem "ruby-debug", :platforms => :mri_18 - gem "nokogiri", :platforms => [:mri_18, :jruby] - -All operations involving groups ([`bundle install`](bundle-install.1.html), `Bundler.setup`, -`Bundler.require`) behave exactly the same as if any groups not -matching the current platform were explicitly excluded. - -### SOURCE - -You can select an alternate Rubygems repository for a gem using the ':source' -option. - - gem "some_internal_gem", :source => "https://gems.example.com" - -This forces the gem to be loaded from this source and ignores any global sources -declared at the top level of the file. If the gem does not exist in this source, -it will not be installed. - -Bundler will search for child dependencies of this gem by first looking in the -source selected for the parent, but if they are not found there, it will fall -back on global sources using the ordering described in [SOURCE PRIORITY][]. - -Selecting a specific source repository this way also suppresses the ambiguous -gem warning described above in -[GLOBAL SOURCES (#source)](#GLOBAL-SOURCES). - -Using the `:source` option for an individual gem will also make that source -available as a possible global source for any other gems which do not specify -explicit sources. Thus, when adding gems with explicit sources, it is -recommended that you also ensure all other gems in the Gemfile are using -explicit sources. - -### GIT - -If necessary, you can specify that a gem is located at a particular -git repository using the `:git` parameter. The repository can be accessed via -several protocols: - - * `HTTP(S)`: - gem "rails", :git => "https://github.com/rails/rails.git" - * `SSH`: - gem "rails", :git => "git@github.com:rails/rails.git" - * `git`: - gem "rails", :git => "git://github.com/rails/rails.git" - -If using SSH, the user that you use to run `bundle install` `MUST` have the -appropriate keys available in their `$HOME/.ssh`. - -`NOTE`: `http://` and `git://` URLs should be avoided if at all possible. These -protocols are unauthenticated, so a man-in-the-middle attacker can deliver -malicious code and compromise your system. HTTPS and SSH are strongly -preferred. - -The `group`, `platforms`, and `require` options are available and behave -exactly the same as they would for a normal gem. - -A git repository `SHOULD` have at least one file, at the root of the -directory containing the gem, with the extension `.gemspec`. This file -`MUST` contain a valid gem specification, as expected by the `gem build` -command. - -If a git repository does not have a `.gemspec`, bundler will attempt to -create one, but it will not contain any dependencies, executables, or -C extension compilation instructions. As a result, it may fail to properly -integrate into your application. - -If a git repository does have a `.gemspec` for the gem you attached it -to, a version specifier, if provided, means that the git repository is -only valid if the `.gemspec` specifies a version matching the version -specifier. If not, bundler will print a warning. - - gem "rails", "2.3.8", :git => "https://github.com/rails/rails.git" - # bundle install will fail, because the .gemspec in the rails - # repository's master branch specifies version 3.0.0 - -If a git repository does `not` have a `.gemspec` for the gem you attached -it to, a version specifier `MUST` be provided. Bundler will use this -version in the simple `.gemspec` it creates. - -Git repositories support a number of additional options. - - * `branch`, `tag`, and `ref`: - You `MUST` only specify at most one of these options. The default - is `:branch => "master"`. For example: - - gem "rails", :git => "https://github.com/rails/rails.git", :branch => "5-0-stable" - - gem "rails", :git => "https://github.com/rails/rails.git", :tag => "v5.0.0" - - gem "rails", :git => "https://github.com/rails/rails.git", :ref => "4aded" - - * `submodules`: - For reference, a [git submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules) - lets you have another git repository within a subfolder of your repository. - Specify `:submodules => true` to cause bundler to expand any - submodules included in the git repository - -If a git repository contains multiple `.gemspecs`, each `.gemspec` -represents a gem located at the same place in the file system as -the `.gemspec`. - - |~rails [git root] - | |-rails.gemspec [rails gem located here] - |~actionpack - | |-actionpack.gemspec [actionpack gem located here] - |~activesupport - | |-activesupport.gemspec [activesupport gem located here] - |... - -To install a gem located in a git repository, bundler changes to -the directory containing the gemspec, runs `gem build name.gemspec` -and then installs the resulting gem. The `gem build` command, -which comes standard with Rubygems, evaluates the `.gemspec` in -the context of the directory in which it is located. - -### GIT SOURCE - -A custom git source can be defined via the `git_source` method. Provide the source's name -as an argument, and a block which receives a single argument and interpolates it into a -string to return the full repo address: - - git_source(:stash){ |repo_name| "https://stash.corp.acme.pl/#{repo_name}.git" } - gem 'rails', :stash => 'forks/rails' - -In addition, if you wish to choose a specific branch: - - gem "rails", :stash => "forks/rails", :branch => "branch_name" - -### GITHUB - -`NOTE`: This shorthand should be avoided until Bundler 2.0, since it -currently expands to an insecure `git://` URL. This allows a -man-in-the-middle attacker to compromise your system. - -If the git repository you want to use is hosted on GitHub and is public, you can use the -:github shorthand to specify the github username and repository name (without the -trailing ".git"), separated by a slash. If both the username and repository name are the -same, you can omit one. - - gem "rails", :github => "rails/rails" - gem "rails", :github => "rails" - -Are both equivalent to - - gem "rails", :git => "git://github.com/rails/rails.git" - -Since the `github` method is a specialization of `git_source`, it accepts a `:branch` named argument. - -### GIST - -If the git repository you want to use is hosted as a Github Gist and is public, you can use -the :gist shorthand to specify the gist identifier (without the trailing ".git"). - - gem "the_hatch", :gist => "4815162342" - -Is equivalent to: - - gem "the_hatch", :git => "https://gist.github.com/4815162342.git" - -Since the `gist` method is a specialization of `git_source`, it accepts a `:branch` named argument. - -### BITBUCKET - -If the git repository you want to use is hosted on Bitbucket and is public, you can use the -:bitbucket shorthand to specify the bitbucket username and repository name (without the -trailing ".git"), separated by a slash. If both the username and repository name are the -same, you can omit one. - - gem "rails", :bitbucket => "rails/rails" - gem "rails", :bitbucket => "rails" - -Are both equivalent to - - gem "rails", :git => "https://rails@bitbucket.org/rails/rails.git" - -Since the `bitbucket` method is a specialization of `git_source`, it accepts a `:branch` named argument. - -### PATH - -You can specify that a gem is located in a particular location -on the file system. Relative paths are resolved relative to the -directory containing the `Gemfile`. - -Similar to the semantics of the `:git` option, the `:path` -option requires that the directory in question either contains -a `.gemspec` for the gem, or that you specify an explicit -version that bundler should use. - -Unlike `:git`, bundler does not compile C extensions for -gems specified as paths. - - gem "rails", :path => "vendor/rails" - -If you would like to use multiple local gems directly from the filesystem, you can set a global `path` option to the path containing the gem's files. This will automatically load gemspec files from subdirectories. - - path 'components' do - gem 'admin_ui' - gem 'public_ui' - end - -## BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS - -The `:source`, `:git`, `:path`, `:group`, and `:platforms` options may be -applied to a group of gems by using block form. - - source "https://gems.example.com" do - gem "some_internal_gem" - gem "another_internal_gem" - end - - git "https://github.com/rails/rails.git" do - gem "activesupport" - gem "actionpack" - end - - platforms :ruby do - gem "ruby-debug" - gem "sqlite3" - end - - group :development, :optional => true do - gem "wirble" - gem "faker" - end - -In the case of the group block form the :optional option can be given -to prevent a group from being installed unless listed in the `--with` -option given to the `bundle install` command. - -In the case of the `git` block form, the `:ref`, `:branch`, `:tag`, -and `:submodules` options may be passed to the `git` method, and -all gems in the block will inherit those options. - -The presence of a `source` block in a Gemfile also makes that source -available as a possible global source for any other gems which do not specify -explicit sources. Thus, when defining source blocks, it is -recommended that you also ensure all other gems in the Gemfile are using -explicit sources, either via source blocks or `:source` directives on -individual gems. - -## INSTALL_IF - -The `install_if` method allows gems to be installed based on a proc or lambda. -This is especially useful for optional gems that can only be used if certain -software is installed or some other conditions are met. - - install_if -> { RUBY_PLATFORM =~ /darwin/ } do - gem "pasteboard" - end - -## GEMSPEC - -The [`.gemspec`](http://guides.rubygems.org/specification-reference/) file is where - you provide metadata about your gem to Rubygems. Some required Gemspec - attributes include the name, description, and homepage of your gem. This is - also where you specify the dependencies your gem needs to run. - -If you wish to use Bundler to help install dependencies for a gem while it is -being developed, use the `gemspec` method to pull in the dependencies listed in -the `.gemspec` file. - -The `gemspec` method adds any runtime dependencies as gem requirements in the -default group. It also adds development dependencies as gem requirements in the -`development` group. Finally, it adds a gem requirement on your project (`:path -=> '.'`). In conjunction with `Bundler.setup`, this allows you to require project -files in your test code as you would if the project were installed as a gem; you -need not manipulate the load path manually or require project files via relative -paths. - -The `gemspec` method supports optional `:path`, `:glob`, `:name`, and `:development_group` -options, which control where bundler looks for the `.gemspec`, the glob it uses to look -for the gemspec (defaults to: "{,*,*/*}.gemspec"), what named `.gemspec` it uses -(if more than one is present), and which group development dependencies are included in. - -When a `gemspec` dependency encounters version conflicts during resolution, the -local version under development will always be selected -- even if there are -remote versions that better match other requirements for the `gemspec` gem. - -## SOURCE PRIORITY - -When attempting to locate a gem to satisfy a gem requirement, -bundler uses the following priority order: - - 1. The source explicitly attached to the gem (using `:source`, `:path`, or - `:git`) - 2. For implicit gems (dependencies of explicit gems), any source, git, or path - repository declared on the parent. This results in bundler prioritizing the - ActiveSupport gem from the Rails git repository over ones from - `rubygems.org` - 3. The sources specified via global `source` lines, searching each source in - your `Gemfile` from last added to first added. diff --git a/man/goruby.1 b/man/goruby.1 index a305a5afce..732ecaa663 100644 --- a/man/goruby.1 +++ b/man/goruby.1 @@ -1,6 +1,6 @@ .\"Ruby is copyrighted by Yukihiro Matsumoto <matz@netlab.jp>. -.Dd April 20, 2017 -.Dt GORUBY \&1 "Ruby Programmer's Reference Guide" +.Dd March 27, 2026 +.Dt GORUBY 1 "Ruby Programmer's Reference Guide" .Os UNIX .Sh NAME .Nm goruby diff --git a/man/index.txt b/man/index.txt deleted file mode 100644 index 400eb02267..0000000000 --- a/man/index.txt +++ /dev/null @@ -1,25 +0,0 @@ -Gemfile(5) gemfile.5 -bundle(1) bundle.1 -bundle-add(1) bundle-add.1 -bundle-binstubs(1) bundle-binstubs.1 -bundle-check(1) bundle-check.1 -bundle-clean(1) bundle-clean.1 -bundle-config(1) bundle-config.1 -bundle-doctor(1) bundle-doctor.1 -bundle-exec(1) bundle-exec.1 -bundle-gem(1) bundle-gem.1 -bundle-info(1) bundle-info.1 -bundle-init(1) bundle-init.1 -bundle-inject(1) bundle-inject.1 -bundle-install(1) bundle-install.1 -bundle-list(1) bundle-list.1 -bundle-lock(1) bundle-lock.1 -bundle-open(1) bundle-open.1 -bundle-outdated(1) bundle-outdated.1 -bundle-package(1) bundle-package.1 -bundle-platform(1) bundle-platform.1 -bundle-pristine(1) bundle-pristine.1 -bundle-remove(1) bundle-remove.1 -bundle-show(1) bundle-show.1 -bundle-update(1) bundle-update.1 -bundle-viz(1) bundle-viz.1 diff --git a/man/irb.1 b/man/irb.1 deleted file mode 100644 index f0a720fbd3..0000000000 --- a/man/irb.1 +++ /dev/null @@ -1,207 +0,0 @@ -.\"Ruby is copyrighted by Yukihiro Matsumoto <matz@netlab.jp>. -.Dd August 11, 2019 -.Dt IRB \&1 "Ruby Programmer's Reference Guide" -.Os UNIX -.Sh NAME -.Nm irb -.Nd Interactive Ruby Shell -.Sh SYNOPSIS -.Nm -.Op Fl -version -.Op Fl dfUw -.Op Fl I Ar directory -.Op Fl r Ar library -.Op Fl E Ar external Ns Op : Ns Ar internal -.Op Fl W Ns Op Ar level -.Op Fl - Ns Oo no Oc Ns inspect -.Op Fl - Ns Oo no Oc Ns multiline -.Op Fl - Ns Oo no Oc Ns singleline -.Op Fl - Ns Oo no Oc Ns echo -.Op Fl - Ns Oo no Oc Ns colorize -.Op Fl - Ns Oo no Oc Ns verbose -.Op Fl -prompt Ar mode -.Op Fl -prompt-mode Ar mode -.Op Fl -inf-ruby-mode -.Op Fl -simple-prompt -.Op Fl -noprompt -.Op Fl -tracer -.Op Fl -back-trace-limit Ar n -.Op Fl - -.Op program_file -.Op argument ... -.Pp -.Sh DESCRIPTION -.Nm -is the REPL(read-eval-print loop) environment for Ruby programs. -.Pp -.Sh OPTIONS -.Bl -tag -width "1234567890123" -compact -.Pp -.It Fl -version -Prints the version of -.Nm . -.Pp -.It Fl E Ar external Ns Op : Ns Ar internal -.It Fl -encoding Ar external Ns Op : Ns Ar internal -Same as `ruby -E' . -Specifies the default value(s) for external encodings and internal encoding. Values should be separated with colon (:). -.Pp -You can omit the one for internal encodings, then the value -.Pf ( Li "Encoding.default_internal" ) will be nil. -.Pp -.It Fl I Ar path -Same as `ruby -I' . -Specifies -.Li $LOAD_PATH -directory -.Pp -.It Fl U -Same as `ruby -U' . -Sets the default value for internal encodings -.Pf ( Li "Encoding.default_internal" ) to UTF-8. -.Pp -.It Fl d -Same as `ruby -d' . -Sets -.Li $DEBUG -to true. -.Pp -.It Fl f -Suppresses read of -.Pa ~/.irbrc . -.Pp -.It Fl w -Same as `ruby -w' . -.Pp -.Pp -.It Fl W -Same as `ruby -W' . -.Pp -.It Fl h -.It Fl -help -Prints a summary of the options. -.Pp -.It Fl r Ar library -Same as `ruby -r'. -Causes irb to load the library using require. -.Pp -.It Fl -inspect -Uses `inspect' for output (default except for bc mode) -.Pp -.It Fl -noinspect -Doesn't use inspect for output -.Pp -.It Fl -multiline -Uses multiline editor module. -.Pp -.It Fl -nomultiline -Doesn't use multiline editor module. -.Pp -.It Fl -singleline -Uses singleline editor module. -.Pp -.It Fl -nosingleline -Doesn't use singleline editor module. -.Pp -.Pp -.It Fl -echo -Show result(default). -.Pp -.It Fl -noecho -Don't show result. -.Pp -.Pp -.It Fl -colorize -Use colorization. -.Pp -.It Fl -nocolorize -Don't use colorization. -.Pp -.Pp -.It Fl -verbose -Show details. -.Pp -.It Fl -noverbose -Don't show details. -.Pp -.It Fl -prompt Ar mode -.It Fl -prompt-mode Ar mode -Switch prompt mode. Pre-defined prompt modes are -`default', `simple', `xmp' and `inf-ruby'. -.Pp -.It Fl -inf-ruby-mode -Uses prompt appropriate for inf-ruby-mode on emacs. -Suppresses --multiline and --singleline. -.Pp -.It Fl -simple-prompt -Makes prompts simple. -.Pp -.It Fl -noprompt -No prompt mode. -.Pp -.It Fl -tracer -Displays trace for each execution of commands. -.Pp -.It Fl -back-trace-limit Ar n -Displays backtrace top -.Ar n -and tail -.Ar n Ns . -The default value is 16. -.El -.Pp -.Sh ENVIRONMENT -.Bl -tag -compact -.It Ev IRBRC -.Pp -.El -.Pp -Also -.Nm -depends on same variables as -.Xr ruby 1 . -.Pp -.Sh FILES -.Bl -tag -compact -.It Pa ~/.irbrc -Personal irb initialization. -.Pp -.El -.Pp -.Sh EXAMPLES -.Dl % irb -.Dl irb(main):001:0> Ic 1 + 1 -.Dl 2 -.Dl irb(main):002:0> Ic def t(x) -.Dl irb(main):003:1> Ic x + 1 -.Dl irb(main):004:1> Ic end -.Dl => :t -.Dl irb(main):005:0> Ic t(3) -.Dl => 4 -.Dl irb(main):006:0> Ic if t(3) == 4 -.Dl irb(main):007:1> Ic p :ok -.Dl irb(main):008:1> Ic end -.Dl :ok -.Dl => :ok -.Dl irb(main):009:0> Ic quit -.Dl % -.Pp -.Sh SEE ALSO -.Xr ruby 1 . -.Pp -.Sh REPORTING BUGS -.Bl -bullet -.It -Security vulnerabilities should be reported via an email to -.Mt security@ruby-lang.org . -Reported problems will be published after being fixed. -.Pp -.It -Other bugs and feature requests can be reported via the -Ruby Issue Tracking System -.Pq Lk https://bugs.ruby-lang.org/ . -Do not report security vulnerabilities -via this system because it publishes the vulnerabilities immediately. -.El -.Sh AUTHORS -Written by Keiju ISHITSUKA. diff --git a/man/ri.1 b/man/ri.1 deleted file mode 100644 index 85a6dfcd53..0000000000 --- a/man/ri.1 +++ /dev/null @@ -1,247 +0,0 @@ -.\"Ruby is copyrighted by Yukihiro Matsumoto <matz@netlab.jp>. -.Dd April 20, 2017 -.Dt RI \&1 "Ruby Programmer's Reference Guide" -.Os UNIX -.Sh NAME -.Nm ri -.Nd Ruby API reference front end -.Sh SYNOPSIS -.Nm -.Op Fl ahilTv -.Op Fl d Ar DIRNAME -.Op Fl f Ar FORMAT -.Op Fl w Ar WIDTH -.Op Fl - Ns Oo Cm no- Oc Ns Cm pager -.Op Fl -server Ns Oo = Ns Ar PORT Oc -.Op Fl - Ns Oo Cm no- Oc Ns Cm list-doc-dirs -.Op Fl -no-standard-docs -.Op Fl - Ns Oo Cm no- Oc Ns Bro Cm system Ns | Ns Cm site Ns | Ns Cm gems Ns | Ns Cm home Brc -.Op Fl - Ns Oo Cm no- Oc Ns Cm profile -.Op Fl -dump Ns = Ns Ar CACHE -.Op Ar name ... -.Sh DESCRIPTION -.Nm -is a command-line front end for the Ruby API reference. -You can search and read the API reference for classes and methods with -.Nm . -.Pp -.Nm -is a part of Ruby. -.Pp -.Ar name -can be: -.Bl -diag -offset indent -.It Class | Module | Module::Class -.Pp -.It Class::method | Class#method | Class.method | method -.Pp -.It gem_name: | gem_name:README | gem_name:History -.El -.Pp -All class names may be abbreviated to their minimum unambiguous form. -If a name is ambiguous, all valid options will be listed. -.Pp -A -.Ql \&. -matches either class or instance methods, while #method -matches only instance and ::method matches only class methods. -.Pp -README and other files may be displayed by prefixing them with the gem name -they're contained in. If the gem name is followed by a -.Ql \&: -all files in the gem will be shown. -The file name extension may be omitted where it is unambiguous. -.Pp -For example: -.Bd -literal -offset indent -ri Fil -ri File -ri File.new -ri zip -ri rdoc:README -.Ed -.Pp -Note that shell quoting or escaping may be required for method names -containing punctuation: -.Bd -literal -offset indent -ri 'Array.[]' -ri compact\e! -.Ed -.Pp -To see the default directories -.Nm -will search, run: -.Bd -literal -offset indent -ri --list-doc-dirs -.Ed -.Pp -Specifying the -.Fl -system , Fl -site , Fl -home , Fl -gems , -or -.Fl -doc-dir -options will limit -.Nm -to searching only the specified directories. -.Pp -.Nm -options may be set in the -.Ev RI -environment variable. -.Pp -The -.Nm -pager can be set with the -.Ev RI_PAGER -environment variable or the -.Ev PAGER -environment variable. -.Pp -.Sh OPTIONS -.Bl -tag -width "1234567890123" -compact -.Pp -.It Fl i -.It Fl - Ns Oo Cm no- Oc Ns Cm interactive -In interactive mode you can repeatedly -look up methods with autocomplete. -.Pp -.It Fl a -.It Fl - Ns Oo Cm no- Oc Ns Cm all -Show all documentation for a class or module. -.Pp -.It Fl l -.It Fl - Ns Oo Cm no- Oc Ns Cm list -List classes -.Nm -knows about. -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm pager -Send output to a pager, -rather than directly to stdout. -.Pp -.It Fl T -Synonym for -.Fl -no-pager . -.Pp -.It Fl w Ar WIDTH -.It Fl -width Ns = Ns Ar WIDTH -Set the width of the output. -.Pp -.It Fl -server Ns Oo = Ns Ar PORT Oc -Run RDoc server on the given port. -The default port is\~8214. -.Pp -.It Fl f Ar FORMAT -.It Fl -format Ns = Ns Ar FORMAT -Use the selected formatter. -The default formatter is -.Li bs -for paged output and -.Li ansi -otherwise. -Valid formatters are: -.Li ansi , Li bs , Li markdown , Li rdoc . -.Pp -.It Fl h -.It Fl -help -Show help and exit. -.Pp -.It Fl v -.It Fl -version -Output version information and exit. -.El -.Pp -Data source options: -.Bl -tag -width "1234567890123" -compact -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm list-doc-dirs -List the directories from which -.Nm -will source documentation on stdout and exit. -.Pp -.It Fl d Ar DIRNAME -.It Fl -doc-dir Ns = Ns Ar DIRNAME -List of directories from which to source -documentation in addition to the standard -directories. May be repeated. -.Pp -.It Fl -no-standard-docs -Do not include documentation from the Ruby standard library, -.Pa site_lib , -installed gems, or -.Pa ~/.rdoc . -Use with -.Fl -doc-dir . -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm system -Include documentation from Ruby's standard library. Defaults to true. -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm site -Include documentation from libraries installed in -.Pa site_lib . -Defaults to true. -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm gems -Include documentation from RubyGems. Defaults to true. -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm home -Include documentation stored in -.Pa ~/.rdoc . -Defaults to true. -.El -.Pp -Debug options: -.Bl -tag -width "1234567890123" -compact -.Pp -.It Fl - Ns Oo Cm no- Oc Ns Cm profile -Run with the Ruby profiler. -.Pp -.It Fl -dump Ns = Ns Ar CACHE -Dump data from an ri cache or data file. -.El -.Pp -.Sh ENVIRONMENT -.Bl -tag -width "USERPROFILE" -compact -.Pp -.It Ev RI -Options to prepend to those specified on the command-line. -.Pp -.It Ev RI_PAGER -.It Ev PAGER -Pager program to use for displaying. -.Pp -.It Ev HOME -.It Ev USERPROFILE -.It Ev HOMEPATH -Path to the user's home directory. -.El -.Pp -.Sh FILES -.Bl -tag -width "USERPROFILE" -compact -.Pp -.It Pa ~/.rdoc -Path for ri data in the user's home directory. -.Pp -.El -.Pp -.Sh SEE ALSO -.Xr ruby 1 , -.Xr rdoc 1 , -.Xr gem 1 -.Pp -.Sh REPORTING BUGS -.Bl -bullet -.It -Security vulnerabilities should be reported via an email to -.Mt security@ruby-lang.org . -Reported problems will be published after being fixed. -.Pp -.It -Other bugs and feature requests can be reported via the -Ruby Issue Tracking System -.Pq Lk https://bugs.ruby-lang.org/ . -Do not report security vulnerabilities -via this system because it publishes the vulnerabilities immediately. -.El -.Sh AUTHORS -Written by -.An Dave Thomas Aq dave@pragmaticprogrammer.com . diff --git a/man/ruby.1 b/man/ruby.1 index 9f0ae05ee9..bc776b8946 100644 --- a/man/ruby.1 +++ b/man/ruby.1 @@ -1,6 +1,6 @@ .\"Ruby is copyrighted by Yukihiro Matsumoto <matz@netlab.jp>. -.Dd April 14, 2018 -.Dt RUBY \&1 "Ruby Programmer's Reference Guide" +.Dd March 27, 2026 +.Dt RUBY 1 "Ruby Programmer's Reference Guide" .Os UNIX .Sh NAME .Nm ruby @@ -25,6 +25,7 @@ .Op Fl - Ns Bro Cm enable Ns | Ns Cm disable Brc Ns - Ns Ar FEATURE .Op Fl -dump Ns = Ns Ar target .Op Fl -verbose +.Op Fl -crash-report Ns = Ns Ar template .Op Fl - .Op Ar program_file .Op Ar argument ... @@ -100,10 +101,10 @@ different character encodings, without dependence on Unicode. .It Sy "Bignums" With built-in bignums, you can for example calculate factorial(400). .Pp -.It Sy "Reflection and domain specific languages" +.It Sy "Reflection and domain-specific languages" Class is also an instance of the Class class. Definition of classes and methods is an expression just as 1+1 is. So your programs can even write and modify programs. -Thus you can write your application in your own programming language on top of Ruby. +Thus, you can write your application in your own programming language on top of Ruby. .Pp .It Sy "Exception handling" As in Java(tm). @@ -257,7 +258,7 @@ Verbose mode is "verbose". It sets the .Li "$VERBOSE" to true. .Fl W Ns -2 is same as +2 is the same as .Fl w . .El @@ -271,6 +272,11 @@ In auto-split mode, Ruby executes .Dl $F = $_.split at beginning of each loop. .Pp +.It Fl -backtrace-limit Ns = Ns Ar num +Limits the maximum length of backtraces to +.Ar num +lines (default -1, meaning no limit). +.Pp .It Fl c Causes Ruby to check the syntax of the script and exit without executing. If there are no syntax errors, Ruby will print @@ -281,6 +287,8 @@ to the standard output. .It Fl -debug Turns on debug mode. .Li "$DEBUG" +and +.Li "$VERBOSE" will be set to true. .Pp .It Fl e Ar command @@ -388,7 +396,7 @@ before executing script. .Pp .It Fl y .It Fl -yydebug -DO NOT USE. +This option is not guaranteed to be compatible. .Pp Turns on compiler debug mode. Ruby will print a bunch of internal state messages during compilation. Only specify this switch you are going to @@ -423,35 +431,39 @@ Dump some information. .Pp Prints the specified target. .Ar target -can be one of; -.Bl -hang -offset indent +can be one of: +.Bl -hang -offset indent -width "version" .It Sy version -version description same as -.Fl -version +Print version description (same as +.Fl -version). .It Sy usage -brief usage message same as -.Fl h +Print a brief usage message (same as +.Fl h). .It Sy help -Show long help message same as -.Fl -help +Show long help message (same as +.Fl -help). .It Sy syntax -check of syntax same as +Check syntax (same as .Fl c -.Fl -yydebug -.It Sy yydebug -compiler debug mode, same as -.Fl -yydebug +.Fl -yydebug). .Pp -Only specify this switch if you are going to debug the Ruby interpreter. -.It Sy parsetree -.It Sy parsetree_with_comment -AST nodes tree +.El .Pp -Only specify this switch if you are going to debug the Ruby interpreter. +Or one of the following, which are intended for debugging the interpreter: +.Bl -hang -offset indent -width "parsetree" +.It Sy yydebug +Enable compiler debug mode (same as +.Fl -yydebug). +.It Sy parsetree +Print a textual representation of the Ruby AST for the program. .It Sy insns -disassembled instructions -.Pp -Only specify this switch if you are going to debug the Ruby interpreter. +Print a list of disassembled bytecode instructions. +.It Sy -optimize +Disable various optimizations to print a list disassembled bytecode instructions. +.It Sy +error-tolerant +Enable error-tolerant parsing, when yydebug or parsetree. +.It Sy +comment +Annotate a textual representation of the Ruby AST for the program with the associated Ruby source code. .El .Pp .It Fl -verbose @@ -462,6 +474,12 @@ variable to true. If this switch is given, and no script arguments (script file or .Fl e options) are present, Ruby quits immediately. +.Pp +.It Fl -crash-report Ns = Ns Ar template +Sets the template of path name to save crash report. +See +.Ev RUBY_CRASH_REPORT +environment variable for details. .El .Pp .Sh ENVIRONMENT @@ -501,6 +519,43 @@ enabled for only mswin32, mingw32, and OS/2 platforms. If this variable is not defined, Ruby refers to .Ev COMSPEC . .Pp +.It Ev RUBY_FREE_AT_EXIT +If set, Ruby tries to free all dynamically allocated memories. +Introduced in Ruby 3.3, default: unset. +.Pp +.It Ev RUBY_BOX +If set to +.Li 1 , +Ruby Box is enabled and users will be able to execute +.Li Ruby::Box.new . +Ruby Box is an experimental feature introduced in Ruby 4.0. +.Pp +.It Ev RUBY_IO_BUFFER_DEFAULT_SIZE +The custom default buffer size of +.Li IO::Buffer . +.Pp +.It Ev RUBY_MAX_CPU +The maximum number of native threads used by M:N Threads scheduler +Introduced in Ruby 3.3, default: 8. +.Pp +.It Ev RUBY_MN_THREADS +If set to +.Li 1 , +M:N Thread scheduler is enabled on the main Ractor. +Introduced in Ruby 3.3, default: unset. +.Pp +.It Ev RUBY_PAGER +The pager command that will be used for +.Fl -help +option. +Introduced in Ruby 3.0, default: +.Ev PAGER +environment variable. +.Pp +.It Ev RUBY_THREAD_TIMESLICE +Sets the default thread time slice (thread quantum) in milliseconds. +Introduced in Ruby 3.4, default: 100ms. +.Pp .It Ev PATH Ruby refers to the .Ev PATH @@ -523,7 +578,7 @@ malloc family of C standard library calls ( .Xr calloc 3 , and .Xr realloc 3 ) . -In this documentatation, the "heap" refers to the Ruby object heap +In this documentation, the "heap" refers to the Ruby object heap of fixed-sized slots, while "malloc" refers to auxiliary allocations commonly referred to as the "process heap". Thus there are at least two possible ways to trigger GC: @@ -545,10 +600,16 @@ Reaching the old malloc limit. .El .Pp There are currently 4 possible areas where the GC may be tuned by -the following 11 environment variables: -.Bl -hang -compact -width "RUBY_GC_OLDMALLOC_LIMIT_GROWTH_FACTOR" -.It Ev RUBY_GC_HEAP_INIT_SLOTS -Initial allocation slots. Introduced in Ruby 2.1, default: 10000. +the following environment variables: +.Bl -hang -compact -width "RUBY_GC_HEAP_n_INIT_SLOTS" +.Pp +.It Ev RUBY_GC_HEAP_ Ns Ar n Ns Ev _INIT_SLOTS +Initial allocation of slots in a specific heap. +The available heaps can be found in the keys of +.Li GC.stat_heap . +.Ar n +is a decimal number between 0 and 4. +Introduced in Ruby 3.3. .Pp .It Ev RUBY_GC_HEAP_FREE_SLOTS Prepare at least this amount of slots after GC. @@ -570,6 +631,12 @@ where R is this factor and N is the number of old objects after the last full GC. Introduced in Ruby 2.1.1, default: 2.0 .Pp +.It Ev RUBY_GC_HEAP_REMEMBERED_WB_UNPROTECTED_OBJECTS_LIMIT_RATIO +Used to calculate the +.Li remembered_wb_unprotected_objects_limit +using a ratio of +.Li old_objects . +Introduced in Ruby 3.3, default: 0.1, minimum: 0.0 .It Ev RUBY_GC_MALLOC_LIMIT The initial limit of young generation allocation from the malloc-family. GC will start when this limit is reached. @@ -586,6 +653,31 @@ GC frequency but increasing malloc growth until RUBY_GC_MALLOC_LIMIT_MAX is reached. Introduced in Ruby 2.1, default: 1.4, minimum: 1.0 (no growth) .Pp +.It Ev RUBY_GC_HEAP_FREE_SLOTS_MIN_RATIO +Allocate additional pages when the number of free slots is +lower than the value +.Li (total_slots * (this ratio)) . +Introduced in Ruby 2.4, default: 0.2, minimum: 0.0, maximum: 1.0 +.Pp +.It Ev RUBY_GC_HEAP_FREE_SLOTS_MAX_RATIO +Allow to free pages when the number of free slots is greater than the value +.Li (total_slots * (this ratio)) . +Introduced in Ruby 2.4, default: 0.4, minimum: +.Li RUBY_GC_HEAP_FREE_SLOTS_MIN_RATIO, +maximum: 1.0 +.Pp +.It Ev RUBY_GC_HEAP_FREE_SLOTS_GOAL_RATIO +Allocate slots to satisfy this formula: +.Li free_slots = total_slots * goal_ratio +In other words, prepare +.Li (total_slots * goal_ratio) +free slots. +if this value is 0.0, then use RUBY_GC_HEAP_GROWTH_FACTOR directly. +Introduced in Ruby 2.4, default: 0.65, minimum: +.Li RUBY_GC_HEAP_FREE_SLOTS_MIN_RATIO, +maximum: +.Li RUBY_GC_HEAP_FREE_SLOTS_MAX_RATIO +.Pp .It Ev RUBY_GC_OLDMALLOC_LIMIT The initial limit of old generation allocation from malloc, a full GC will start when this limit is reached. @@ -603,6 +695,21 @@ GC frequency but increasing malloc growth until RUBY_GC_OLDMALLOC_LIMIT_MAX is reached. Introduced in Ruby 2.1, default: 1.2, minimum: 1.0 (no growth) .Pp +.It Ev RUBY_SHARED_FIBER_POOL_FREE_STACKS +Frees stacks of pooled fibers, if set to 1. +Do not free the stacks if set to 0. +Introduced in Ruby 2.7, default: 1 (no growth) +.Pp +.It Ev RUBY_SHARED_FIBER_POOL_MAXIMUM_COUNT +If set to a non-negative integer, the shared fiber pool cannot allocate more +than that many stacks; further fiber creation may fail with +.Va FiberError . +Unset or 0 means no explicit cap (subject to process limits). +.Pp +.It Ev RUBY_SHARED_FIBER_POOL_MINIMUM_COUNT +Initial and minimum growth chunk size for the shared fiber pool (stacks). +Unset uses the implementation default. +.Pp .El .Sh STACK SIZE ENVIRONMENT Stack size environment variables are implementation-dependent and @@ -618,11 +725,11 @@ All values are specified in bytes. .Bl -hang -compact -width "RUBY_THREAD_MACHINE_STACK_SIZE" .It Ev RUBY_THREAD_VM_STACK_SIZE VM stack size used at thread creation. -default: 131072 (32-bit CPU) or 262144 (64-bit) +default: 524288 (32-bit CPU) or 1048576 (64-bit) .Pp .It Ev RUBY_THREAD_MACHINE_STACK_SIZE Machine stack size used at thread creation. -default: 524288 or 1048575 +default: 524288 or 1048576 .Pp .It Ev RUBY_FIBER_VM_STACK_SIZE VM stack size used at fiber creation. @@ -633,6 +740,72 @@ Machine stack size used at fiber creation. default: 262144 or 524288 .Pp .El +.Sh CRASH REPORT ENVIRONMENT +.Pp +.Bl -tag -compact -width "RUBY_CRASH_REPORT" +.It Ev RUBY_CRASH_REPORT +The template of path name to save crash report. +default: none +.El +.Ss Naming crash report files +The template can contain +.Li \fB%\fP +specifiers which are substituted by the following values when a crash +report file is created: +.Pp +.Bl -hang -compact -width "%NNN" +.It Li \fB%%\fP +A single +.Li \fB%\fP +character. +.It Li \fB%e\fP +Basename of executable. +.It Li \fB%E\fP +Pathname of executable, +with slashes (\fB/\fP) replaced by exclamation marks (\fB!\fP). +.It Li \fB%f\fP +Basename of the program name, +.Li "$0" . +.It Li \fB%F\fP +Pathname of the program name, +.Li "$0", +with slashes (\fB/\fP) replaced by exclamation marks (\fB!\fP). +.It Li \fB%p\fP +PID of dumped process. +.It Li \fB%t\fP +Time of dump, expressed as seconds since the +Epoch, 1970-01-01 00:00:00 +0000 (UTC). +.It Li \fB%NNN\fP +A character code in octal. +.El +.Pp +A single +.Li \fB%\fP +at the end of the template is dropped from the core filename, as is +the combination of a +.Li \fB%\fP +followed by any character other than those listed above. All other +characters in the template become a literal part of the core filename. +The template may include \(aq/\(aq characters, which are interpreted +as delimiters for directory names. +.Ss Piping crash reports to a program +If the first character of this file is a pipe symbol (\fB|\fP), +then the remainder of the line is interpreted as the command-line for +a program (or script) that is to be executed. +.Pp +The pipe template is split on spaces into an argument list before the +template parameters are expanded. +.Sh MISC ENVIRONMENT +.Pp +.Bl -hang -compact -width "RUBY_TCP_NO_FAST_FALLBACK" +.It Ev RUBY_TCP_NO_FAST_FALLBACK +If set to +.Li 1 , +disables the fast fallback feature by default in TCPSocket.new and Socket.tcp. +When set to +.Li 0 +or left unset, the fast fallback feature is enabled. +Introduced in Ruby 3.4, default: unset. .Sh SEE ALSO .Bl -hang -compact -width "https://www.ruby-toolbox.com/" .It Lk https://www.ruby-lang.org/ @@ -660,5 +833,5 @@ Ruby is designed and implemented by .An Yukihiro Matsumoto Aq matz@netlab.jp . .Pp See -.Aq Lk https://bugs.ruby-lang.org/projects/ruby/wiki/Contributors +.Aq Lk https://github.com/ruby/ruby/graphs/contributors for contributors to Ruby. |