[ANN] RubyGems 0.6.1

C

Chad Fowler

Hi All...

We've fixed a couple of small but nasty bugs on 0.6.0. We're doing a
small point-release in support of a couple of developers who would like
to go ahead and release gems but are crippled by these problems.
Excuse the traffic (and the need to redownload RubyGems), but please do
grab the latest:

http://rubyforge.org/frs/?group_id=126

Thanks to everyone who has given us bug reports, feature ideas, and
CODE so far!
Chad (for the RubyGems team)
 
C

Charles Comstock

Hi All...

We've fixed a couple of small but nasty bugs on 0.6.0. We're doing a
small point-release in support of a couple of developers who would like
to go ahead and release gems but are crippled by these problems.
Excuse the traffic (and the need to redownload RubyGems), but please do
grab the latest:

http://rubyforge.org/frs/?group_id=126

Thanks to everyone who has given us bug reports, feature ideas, and
CODE so far!
Chad (for the RubyGems team)

--

Something minor but I just noticed that gem doesn't seem to support a --version
tag. I see it has it on --rubygems-info but maybe --version should alias that
or something. Not critical or anything but seems to make more sense to me.
Charles Comstock
 
C

Chad Fowler

--

Something minor but I just noticed that gem doesn't seem to support a --version
tag. I see it has it on --rubygems-info but maybe --version should alias that
or something. Not critical or anything but seems to make more sense to me.
Charles Comstock

I agree, but we're using --version to specify gem versions. I think
it makes sense to minimize typing for this operation as opposed to
finding out the rubygems version, since the former will be used a lot
more. Do you think we need to alias --rubygems-version or something?

Chad
 
G

Gavin Sinclair

I agree, but we're using --version to specify gem versions. I think it
makes sense to minimize typing for this operation as opposed to finding
out the rubygems version, since the former will be used a lot more. Do
you think we need to alias --rubygems-version or something?

Not sure what you mean there, Chad. gem --version currently does nothing,
and I don't know what "we're using --version to specify gem versions"
means.

Hang on, the penny just dropped. I left my mistake in there to
demonstrate that in my mind specifying a version on the gem command-line
is a very rare experience to me. When I want to install a specific
version of something I use, for instance:

gem -i pqa-0.5

Of course there's

gem -i pqa --version '< 0.7'

but like I say, I never really have a use for that.

Thus I support using --version to convey information about RubyGems, as
anyone accustomed to command-line tools will expect that.

Gavin
 
G

Gavin Sinclair

Thus I support using --version to convey information about RubyGems, as
anyone accustomed to command-line tools will expect that.

Quick follow-up with suggestion.

-V, --gem-version Specify version of gem to perform operation on
-v, --version Show RubyGems version and exit

I think that's pretty reasonable. Now what about --rubygems-info? Keep
it as it is? Roll it into --version and get rid of it?

I favour getting rid of --rubygems-info (it's awkward to type) and just
having

-v, --version Display RubyGems information and exit

What sayeth the mob?

Gavin
 
C

Charles Comstock

I agree, but we're using --version to specify gem versions. I think
it makes sense to minimize typing for this operation as opposed to
finding out the rubygems version, since the former will be used a lot
more. Do you think we need to alias --rubygems-version or something?

Oh I didn't even see that use of version. Hmm. Maybe if there is no
other options and you get version it should spit out the version info?
I can't think of how that would be incompatible, course it might be
slightly confusing if it was documented, but it would get the standard
console app behavior one would expect. Just a thought.

Charlie
 
C

Chad Fowler

Quick follow-up with suggestion.

-V, --gem-version Specify version of gem to perform operation on
-v, --version Show RubyGems version and exit

I think that's pretty reasonable. Now what about --rubygems-info? Keep
it as it is? Roll it into --version and get rid of it?

I favour getting rid of --rubygems-info (it's awkward to type) and just
having

-v, --version Display RubyGems information and exit

I guess I'm not the mob, but I would advocate --rubygems-version
replacing --rubygems-info. I use the --version flag on a regular
basis, but there is definitely something to be said for consistency
with other tools (which I think would also make the case for doing
away with --help-options in favor of --help.

Chad
 
G

Gavin Sinclair

I guess I'm not the mob, but I would advocate --rubygems-version
replacing --rubygems-info. I use the --version flag on a regular
basis, but there is definitely something to be said for consistency with
other tools (which I think would also make the case for doing away with
--help-options in favor of --help.

Wouldn't you rather type -V than --version? Or is that not an intuitive
enough alias for --gem-version?

I think you're right about --help. I'll try a rearrangement in CVS and
see what you think.

Gavin
 
J

Jim Weirich

Chad said:
I agree, but we're using --version to specify gem versions. I think
it makes sense to minimize typing for this operation as opposed to
finding out the rubygems version, since the former will be used a lot
more. Do you think we need to alias --rubygems-version or something?

There has been some talk about rearranging the gem option structure to
mirror cvs, e.g. gem install --remote, or gem list --local. Cvs will
differentiate between options on the "cvs" command, and options on the
sub-commands. In that case, we could support both ...

gem --version
and
gem install gem-name --version ">= 1.0"

BTW, I favor the move to a cvs-like command structure (if anyone asks).
 
C

Chad Fowler

There has been some talk about rearranging the gem option structure to
mirror cvs, e.g. gem install --remote, or gem list --local. Cvs will
differentiate between options on the "cvs" command, and options on the
sub-commands. In that case, we could support both ...

gem --version
and
gem install gem-name --version ">= 1.0"



Yea, that would really help in this case, wouldn't it?

Chad
 
R

Richard Kilmer

Yea, that would really help in this case, wouldn't it?

Chad

Yes it would, and would help with the growing number of commands and the
size of the returned --help data.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

[ANN] RubyGems 1.3.4 0
[ANN] RubyGems 1.3.1 12
[ANN] RubyGems 1.3.0 14
[ANN] RubyGems 1.0.1 11
[ANN] RubyGems 1.2.0 48
[ANN] HighLine 0.6.1 8
ANN: RubyGems 0.9.4 1
[ANN] RubyGems 1.1.1 20

Members online

No members online now.

Forum statistics

Threads
474,146
Messages
2,570,832
Members
47,374
Latest member
EmeliaBryc

Latest Threads

Top