Man page - bundle-binstubs(1)
Packages contas this manual
- bundle-add(1)
- bundle-doctor(1)
- bundle-update(1)
- bundle(1)
- bundle-list(1)
- bundle-check(1)
- bundle-open(1)
- bundle-show(1)
- bundle-install(1)
- bundler(1)
- bundle-binstubs(1)
- bundle-outdated(1)
- bundle-pristine(1)
- bundle-init(1)
- bundle-gem(1)
- bundle-platform(1)
- bundle-info(1)
- bundle-remove(1)
- bundle-inject(1)
- gemfile(5)
- bundle-exec(1)
- bundle-lock(1)
- bundle-clean(1)
- bundle-viz(1)
- bundle-cache(1)
- bundle-config(1)
apt-get install ruby-bundler
Manual
| BUNDLE-BINSTUBS(1) | General Commands Manual | BUNDLE-BINSTUBS(1) |
NAME
bundle-binstubs - Install the binstubs of the listed gems
SYNOPSIS
bundle binstubs GEM_NAME [--force] [--path PATH] [--standalone] [--all-platforms]
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[=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=SHEBANG
- Specify a different shebang executable name than the default (default 'ruby')
- --all
- Create binstubs for all gems in the bundle.
- --all-platforms
- Install binstubs for all platforms.
| March 2025 |