Option to Print only Outdated or Missing Gems
Reported by Matthew O'Connor | November 11th, 2008 @ 10:36 AM | in 1.0 Release
It would be nice if there was an option similar to --print-rogue-gems which printed only the missing/outdated gems for your project.
Comments and changes to this ticket
-
Alf Mikula December 16th, 2008 @ 04:48 PM
I agree, this would be really nice. Right now, I'm using script/runner under rails to run GemInstaller::autogem, and using that as a conditional in my shell script to determine whether to run geminstaller under sudo. It would be great to have a -n or --no-install or --check or something similar to do this.
-
Jeff Whitmire January 23rd, 2009 @ 12:17 PM
I have a patch for this. It's mostly untested but it works really fast since it's only checking against the local gems (no remoteness involved). I've been meaning to get it to Chad and will do so soon.
-
Jeff Whitmire February 4th, 2009 @ 06:21 PM
I'm not sure this exactly fits the request here, but I finally got around to redoing my patch with some test coverage this time. It adds a -o option that acts much like the print-rogue-gems option. It will simply list any local gems you have installed that are newer than the ones specified in the config file.
It will honor the specification and only print gems that do not fit. If you have version >= 1.0.0 for a gem, it will not list a 2.0 gem as outdated in that case, but if the version specification is an exact match it will.
-
Chad Woolley February 16th, 2009 @ 03:10 AM
- Milestone set to “1.0 Release”
- State changed from “new” to “open”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
GemInstaller
http://geminstaller.rubyforge.org
Chad Woolley
Matthew O'Connor