Just had one final question… what is the difference between:
bundle exec “command”
and
directly running the command?
Like for me bundle exec rspec throws and error while rspec does not.
Just had one final question… what is the difference between:
bundle exec “command”
and
directly running the command?
Like for me bundle exec rspec throws and error while rspec does not.
I’ve only recently started with Ruby on Rails myself. Check out my
insights, procedures, and deployed projects at
http://www.jasonhsu.com/ror.html
. I put this page together partly as a resource for the Ruby on Rails
community but mostly as a reference for myself.
The things I insist on:
On Wed, Nov 30, 2011 at 5:44 PM, Somnath M.
[email protected]wrote:
Just had one final question… what is the difference between:
bundle exec “command”
and
directly running the command?
“bundle exec” makes sure that you’re using the executables that ship
along
with
the gem installed by bundler while running only the command uses the one
recognized by your system.
Like for me bundle exec rspec throws and error while rspec does not.
This usually happens when the rspec bundle exec runs is of a different
version.
Try getting the version of the rspec executable that works and change
your
Gemfile
to use that rspec version. Run bundle install and try running rspec
again
with
bundle exec.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
–
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs