Hey David, thanks a lot for your reply. On Fri, Apr 6, 2012 at 8:51 PM, David Dollar <[email protected]> wrote: > The .gems solution was non-deterministic in the normal use case. If someone > specified "sinatra" in their .gems file, they would often end up with a > completely different version in production than they were using in > development. Sure you could specify an exact version of every gem in your > .gems file, but few people did and it's a huge pain to maintain.
Yes, I understand how frustrating that would be. Would requiring specific versions solve it or you think people would keep making mistakes? > Bundler splits dependency declaration into what the developer cares about > (Gemfile) and an exact specification of each version that should be > installed (Gemfile.lock). This maintains dev/prod parity without the > maintenance overhead of curating a specific list of gem versions yourself. > It also has the advantage of not being specific to Heroku. Understood. I may add that it has the disadvantage of requiring a very heavy dependency (Bundler), but I guess Heroku's best interest is to push for the standardization of Bundler, as it simplifies its operations. It would be great for me if the .gems manifest were supported in its "strict" version, but I understand I'm part of a tiny minority. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
