bundle-inject – Add named gem(s) with version requirements to Gemfile Synopsisbundle inject [GEM] [VERSION] DescriptionAdds 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…
bundle-init – Generates a Gemfile into the current working directory Synopsisbundle init [–gemspec=FILE] DescriptionInit 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…
bundle-info – Show information for the given gem in your bundle Synopsisbundle info [GEM] [–path] DescriptionPrint the basic information about the provided GEM such as homepage, version, path and summary. Options–path Print the path of the given gem
bundle-gem – Generate a project skeleton for creating a rubygem Synopsisbundle gem GEM_NAME OPTIONS DescriptionGenerates 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…
bundle-exec – Execute a command in the context of the bundle Synopsisbundle exec [–keep-file-descriptors] command DescriptionThis 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)]…
bundle-doctor – Checks the bundle for common problems Synopsisbundle doctor [–quiet] [–gemfile=GEMFILE] DescriptionChecks 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 •…
bundle-config – Set bundler configuration options Synopsisbundle config [list|get|set|unset] [name [value]] DescriptionThis command allows you to interact with Bundler’s configuration system. Bundler loads configuration settings in this order: 1. Local config (app/.bundle/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…
bundle-clean – Cleans up unused gems in your bundler directory Synopsisbundle clean [–dry-run] [–force] DescriptionThis 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…
bundle-check – Verifies if dependencies are satisfied by installed gems Synopsisbundle check [–dry-run] [–gemfile=FILE] [–path=PATH] Descriptioncheck 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…
bundle-cache – Package your needed .gem files into your application Synopsisbundle cache DescriptionCopy 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 GemsThe bundle cache command can…
bundle-binstubs – Install the binstubs of the listed gems Synopsisbundle binstubs GEM_NAME [–force] [–path PATH] [–standalone] DescriptionBinstubs 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…
bundle-add – Add gem to the Gemfile and run bundle install Synopsisbundle add GEM_NAME [–group=GROUP] [–version=VERSION] [–source=SOURCE] [–git=GIT] [–branch=BRANCH] [–skip-install] [–strict] [–optimistic] DescriptionAdds 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"…
bash, :, ., [, alias, bg, bind, break, builtin, caller, cd, command, compgen, complete, compopt, continue, declare, dirs, disown, echo, enable, eval, exec, exit, export, false, fc, fg, getopts, hash, help, history, jobs, kill, let, local, logout, mapfile, popd, printf, pushd, pwd, read, readonly, return, set, shift, shopt, source, suspend, test, times, trap, true, type,…
bash, :, ., [, alias, bg, bind, break, builtin, caller, cd, command, compgen, complete, compopt, continue, declare, dirs, disown, echo, enable, eval, exec, exit, export, false, fc, fg, getopts, hash, help, history, jobs, kill, let, local, logout, mapfile, popd, printf, pushd, pwd, read, readonly, return, set, shift, shopt, source, suspend, test, times, trap, true, type,…
build-jar-repository – create a symbolic link to a JAR Synopsisbuild-jar-repository [OPTION]… DIRECTORY JAR|artifact-coordinates DescriptionBuild a JAR repository in the named directory by copying files or creating symbolic links. The JARs can be identified by their names or Maven artifact coordinates. Artifact coordinates specify Maven artifact and are in format groupId:artifactId[:extension[:classifier]]:version. If extension is omitted then…
build-classpath – build a Java CLASSPATH Synopsisbuild-classpath JAR|artifact-coordinates [JAR|artifact-coordinates …] DescriptionSmall utility to build a Java CLASSPATH with the named JARs or Maven artifact coordinates. Artifact coordinates specify Maven artifact and are in format groupId:artifactId[:extension[:classifier]]:version. If extension is omitted then "jar" is used. If classifier is omitted then empty classifier is used. For more information…
bugzilla – command-line interface to Bugzilla over XML-RPC Synopsisbugzilla [options] [command] [command-options] Descriptionbugzilla is a command-line utility that allows access to the XML-RPC interface provided by Bugzilla. command is one of: * login – log into the given bugzilla instance * new – create a new bug * query – search for bugs matching given…
bugpoint – automatic test case reduction tool Synopsisbugpoint [options] [input LLVM ll/bc files] [LLVM passes] –args program arguments Descriptionbugpoint narrows down the source of problems in LLVM tools and passes. It can be used to debug three types of failures: optimizer crashes, miscompilations by optimizers, or bad native code generation (including problems in the static…
bugpoint – automatic test case reduction tool Synopsisbugpoint [options] [input LLVM ll/bc files] [LLVM passes] –args program arguments Descriptionbugpoint narrows down the source of problems in LLVM tools and passes. It can be used to debug three types of failures: optimizer crashes, miscompilations by optimizers, or bad native code generation (including problems in the static…
buffer – very fast reblocking program Syntaxbuffer [-S size] [-b blocks] [-s size] [-m size] [-p percentage] [-u microseconds] [-B] [-t] [-Z] [-i filename] [-o filename] Options-i filename Use the given file as the input file. The default is stdin. -o filename Use the given file as the output file. The default is stdout. -S…