<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I would follow the new advice. We are running a Ruby Padrino application that is now more than three years old. By committing the Gemfile.lock we have been able to keep all our remote servers and developer environments the same. We then can control upgrades to either the whole stack or single gems by bundling and then updating the Gemfile.lock and recommitting.<div class=""><br class=""><div class="">
Regards,
</div><div class=""><br class="webkit-block-placeholder"></div><div class="">Jason Hooper</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 10 May 2017, at 11:08, Asfand Qazi <<a href="mailto:ayqazi@gmail.com" class="">ayqazi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello,<div class=""><br class=""></div><div class="">I have a question regarding Bundler, developing gems, and Gemfile.lock . It is a question I thought I had the answer to, but apparently not.</div><div class=""><br class=""></div><div class="">I USED to believe that you do not check in Gemfile.lock, so as to allow situations during development to occur where your gem is used with a version of a dependency that you did not expect, therefore allowing possibly breaking interface changes to dependencies to be made apparent. This is what Mr. Katz says here, in 2010: <a href="http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/" class="">http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/</a>.</div><div class=""><br class=""></div><div class="">However, checking the latest bundler docs, here we read something different: <a href="http://bundler.io/v1.14/guides/creating_gem.html" class="">http://bundler.io/v1.14/guides/creating_gem.html</a></div><div class=""><br class=""></div><div class="">"By running bundle install, Bundler will generate the extremely important Gemfile.lock file. This file is responsible for ensuring that every system this library is developed on has the exact same gems so it should always be checked into version control. For more information on this file read “THE GEMFILE.LOCK” section of the bundle install manpage."</div><div class=""><br class=""></div><div class="">Que?</div><div class=""><br class=""></div><div class="">What do y'all think? Follow the old advice, or the new advice?</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class="gmail-Apple-interchange-newline">Regards,<br class=""> Asfand Qazi<br class=""> The DevOps Doctors<br class=""><br class=""> E: <a href="mailto:asfand@thedevopsdoctors.com" target="_blank" class="">asfand@thedevopsdoctors.com</a><br class=""> W: <a href="https://www.thedevopsdoctors.com/" target="_blank" class="">https://www.thedevopsdoctors.com/</a><br class="">
</div></div>
_______________________________________________<br class="">Chat mailing list<br class=""><a href="mailto:Chat@lists.lrug.org" class="">Chat@lists.lrug.org</a><br class="">Archives: http://lists.lrug.org/pipermail/chat-lrug.org<br class="">Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org<br class="">List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org<br class=""></div></blockquote></div><br class=""></div></body></html>