Updating gem

When you install a gem to the system, Rubygems creates wrappers for every executable that the gem makes available.When you run an executable from the command line without bundle exec, this wrapper invokes Rubygems, which then uses the normal Rubygems activation mechanism to invoke the gem's executable.You can comment below, or link to this permanent URL from your own site.Recently, an upgrade to Rake (from version 0.8.7 to version 0.9.0) has re-raised the issue of dependencies and versioning in the Ruby community.I wanted to take the opportunity to reiterate some of the things I talked about back when working on Bundler 1.0.First, I'll lay out some basic rules for the road, and then go into some detail about the rationale.


$ sass -v Haml/Sass 3.0.9 (Classy Cassidy) $ sudo gem uninstall -Iax sass Removing sass Removing sass-convert Removing scss Successfully uninstalled sass-3.2.0.alpha.35 $ sass -v Haml/Sass 3.0.9 (Classy Cassidy) (Was expecting an error here) $ sudo gem install sass --pre Successfully installed sass-3.2.0.alpha.35 1 gem installed Installing ri documentation for sass-3.2.0.alpha.35...Installing RDoc documentation for sass-3.2.0.alpha.35... $ sass -v Haml/Sass 3.0.9 (Classy Cassidy) Old Edit if you've still got stuff left over it sounds like there's been a manual install, another gem has set something up or you've installed it from a package.



Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>