[Rubygems-developers] [PATCH] Two changes to the gem list command

Chad Woolley thewoolleyman at gmail.com
Fri Aug 1 20:39:10 EDT 2008


On Fri, Aug 1, 2008 at 2:00 PM, Bjørn Arild Mæland
<bjorn.maeland at gmail.com> wrote:
> I've made a couple of very small patches that deals with the list command.

I haven't looked closely, but I think these are good patches.  i've
worked around these exact issues in GemInstaller when I interact with
the RubyGems API, and these patches would make some of my code go
away.  They will break me, but I have to look at some other recent
changes anyway which broke me (apparently tty, more brittle
output-parsing stuff like this).

Couple of concerns:
* They will likely break other people who use the API, so there should
be good warning before they are applied/released - and perhaps a minor
version bump in trunk when they are applied, so it is easy to write
version specific code to use the patches or not (and thus maintain
backward compatibility by still using my previous workarounds).
* Not sure about the return code of 1.  No results isn't really an
error.  ALso, it might be useful to distinguish it from other (real?)
errors or exit conditions.  Are there any?  Maybe a different return
code than 1?

-- Chad


More information about the Rubygems-developers mailing list