bundle outdated On Sunday, March 2, 2014 12:18:39 AM UTC+4, Jedrin wrote: > > > I was asked an interview question on how I would keep an app's gems up to > date. Suppose there was a new gem because of some security issue for > instance ? > > Where I worked before, we locked the gems in the gem file with a > particular version with the notation of something like: > gem 'multi_json' , '~> 1.8.2' > > That way we would not get surprises when we updated the gems as changes > could occur without our being able to know what they where and the app > would be unstable. I've also found when some one gives you an app to work > on and it has not been used for several months, if the gemfile has no > versions on the gems then you will have a hard time figuring out why > everything is broken or what gem version it used to work in. > > I did not find there to be an easy answer to this question given that a > gem file can contain many gems and knowing when to go to a new version is > not clear. At a certain point in time between projects, we might try to > update the gems. Is there a simple way to tell how far out of date the gems > in the gemfile are using a command of some kind ? > > > >
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/def04ccd-fbd3-44f9-90a6-d46619d6ed2d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
