Advise not to track track Gemfile.lock for gem development

radar / guides

Guides for Ruby and Elixir and whatever else I feel like

1.52k stars 164 forks source link

Advise not to track track Gemfile.lock for gem development #74

Closed nilbus closed 6 years ago

nilbus commented 6 years ago

Provide an explanation
Update all exmaples to match

Further explanation from Bundler's author, Yehuda Katz:
http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/

Fixes #14 Closes #23, now obsolete

nilbus commented 6 years ago

Of course this patch doesn't bring the entire guide up to date, but I think that's a separate endeavor that will require some more dedicated time. Some things I happened to notice while working:

Missing authors/emails in gemspec now make gemspecs invalid and unbuildable
References to rubyforge

radar commented 6 years ago

Thanks @nilbus! I can probably look at fixing up the other things.

matthewd commented 6 years ago

FYI, this is no longer the official advice... see https://github.com/bundler/bundler/issues/5879 & friends.

radar commented 6 years ago

Thanks @matthewd. Probably high time I removed this guide from this repo, as the Bundler guide is a more up-to-date copy of that same guide.