[LRUG] Gemfile.lock for gems - to check in or not to check in, that is the question

[Asfand Qazi]

Hello,

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.

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:
http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
.

However, checking the latest bundler docs, here we read something
different: http://bundler.io/v1.14/guides/creating_gem.html

"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."

Que?

What do y'all think? Follow the old advice, or the new advice?

Thanks

Regards,
    Asfand Qazi
    The DevOps Doctors

    E: asfand at thedevopsdoctors.com
    W: https://www.thedevopsdoctors.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20170510/ba3967e6/attachment.html>