Re:How fresh are your gems?
by jwilliams on Thursday September 29, 2011 @02:24AM
(#3051373)
I mistakenly thought that was a deprecated feature, but I've taken a look. Not getting the same results at the moment (1.1 won't let me update at all at the moment), but I'll see if I can merge/collaborate. Thanks for the pointer.
Re:How fresh are your gems?
by tomfakes on Thursday September 29, 2011 @12:20AM
(#3051112)
There's a cool site here http://www.bundlewatcher.com/ that can read your bundle definition and provides a RSS feed of updates to all your gems.
I have all my gems locked on specific versions to avoid surprises, and this site shows me when there are updates and I can decide to update my bundle to use the updates.
Re:How fresh are your gems?
by jwilliams on Thursday September 29, 2011 @12:04AM
(#3051080)
Doesn't keep me up at night, but it was something I was doing manually and I thought better off scripted. Even with fuzzy/handwave "~> 1.1.1" specifications you can end up off the most current version. I've got a handful of projects on the go and as a rule I don't like to let them go stale.
Re:How fresh are your gems?
by beilabs on Thursday September 29, 2011 @12:25AM
(#3051119)
Yes, that's correct.
Personally I always assign the working version numbers to the Gemfile. What happens in say a years time when you're meant to come back and maintain the site? New versions could mean a drastically broken system and you won't be maintaining a contracts codebase if you are not getting paid to do so.
Re:How fresh are your gems?
by Volpe on Thursday September 29, 2011 @12:40AM
(#3051157)
The .lock file will have the versions that are currently bundled, so you can always check what versions are bundled there. But I guess that requires a bit of messing around, where as what you do seems quite straight forward.
Re:How fresh are your gems?
by beilabs on Thursday September 29, 2011 @12:57AM
(#3051184)
Yes but if the repository is cloned with a lock file, when you bundle install, the lock file is then updated with your new gem versions if you have not specified a specific gem version number.
Re:How fresh are your gems?
by nixme on Thursday September 29, 2011 @11:56AM
(#3052941)
Why not just put an explicit version number directly in the Gemfile. Seems easer than vendoring the gem and bloating the repo (unless you're worried about old versions being yanked from rubygems).
I have all my gems locked on specific versions to avoid surprises, and this site shows me when there are updates and I can decide to update my bundle to use the updates.
If you can, include the stack and the output of `gem environment`. Plus (if they are public) the links to the Gemfile and Gemfile.lock.
I have bundle update as a part of my build/release process, if things break, I either update, or freeze the version.
How do other people deal with this?
Personally I always assign the working version numbers to the Gemfile. What happens in say a years time when you're meant to come back and maintain the site? New versions could mean a drastically broken system and you won't be maintaining a contracts codebase if you are not getting paid to do so.