The sandbox plugin for rubygems helps you manage your command-line
tools and their dependencies. Sandboxed gems are installed in their
own private rubygem repositories with all of their dependencies. This
means that you don’t have to have a rat’s nest of gems in your global
repository in order to run popular command-tools like rdoc, flog,
flay, rcov, etc.
gem sandbox has the following sub-commands:
install gem_name … - install 1 or more gems
plugin gem_name plugin_name … - install a gem and plugins for it
remove gem_name … - uninstall 1 or more gems
help - show this output
Once you install gem sandbox will output something like:
Copy the following scripts to any directory in your path to use
The sandbox plugin for rubygems helps you manage your command-line
tools and their dependencies. Sandboxed gems are installed in their
own private rubygem repositories with all of their dependencies. This
means that you don’t have to have a rat’s nest of gems in your global
repository in order to run popular command-tools like rdoc, flog,
flay, rcov, etc.
Most people die of a sort of creeping common sense, and discover when it
is too late that the only things one never regrets are one’s mistakes.
- Oscar Wilde
Isolate is for creating a private gem repo per project, usually for
development (but also deployment). Isolate also will automatically
install/update/cleanup as needed on every run (and it is fast about it
too).
rubygems-sandbox is only oriented around “isolating” a single gem
utility / command-line tool and its dependencies and is entirely static
once set up. It is really meant for tools like flog, flay, rcov, rdoc,
etc.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.