<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ruby Gems Bundler on Roger Welin</title><link>https://rogerwelin.github.io/categories/ruby-gems-bundler/</link><description>Recent content in Ruby Gems Bundler on Roger Welin</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Tue, 17 Mar 2015 20:03:43 +0000</lastBuildDate><atom:link href="https://rogerwelin.github.io/categories/ruby-gems-bundler/feed.xml" rel="self" type="application/rss+xml"/><item><title>Rubygems made easy with bundler</title><link>https://rogerwelin.github.io/2015/03/17/rubygems-made-easy-with-bundler/</link><pubDate>Tue, 17 Mar 2015 20:03:43 +0000</pubDate><guid>https://rogerwelin.github.io/2015/03/17/rubygems-made-easy-with-bundler/</guid><description>&lt;p&gt;One thing with Ruby I don&amp;rsquo;t quite like (and many with me) are the Ruby gems. The one thing thats great with gems is that it&amp;rsquo;s almost as with CPAN, if you have a problem - there&amp;rsquo;s a gem for that! But I don&amp;rsquo;t like the idea of installing libraries system-wide. If installed with sudo it&amp;rsquo;s a security risk. And my belief is that libraries are supposed to be used by demand when an application needs them. For example Java + maven and Node.js and NPM is a good example of those getting this right. Let&amp;rsquo;s say you want to share a ruby project, the problem is that person must have the same set of gems installed to be able to run your program, and maybe he&amp;rsquo;s installing a newer version of that gem that you was testing on. Not good! Fortunately we have Bundler to help us keep track of gems and it&amp;rsquo;s dependencies that solves this problem.&lt;/p&gt;</description></item></channel></rss>