Bug #2355

Please update rubygems!

Added by Yusuke Endoh over 4 years ago. Updated almost 3 years ago.

[ruby-core:26679]
Status:Closed
Priority:Urgent
Assignee:Eric Hodel
Category:lib
Target version:2.0.0
ruby -v:ruby 1.9.2dev (2009-11-11 trunk 25717) [i686-linux] Backport:

Description

=begin
On the trunk:

$ gem19 install gemcutter
ERROR: Error installing gemcutter:
gemcutter requires RubyGems version >= 1.3.5

Some standard libraries including rubygems are developed in maintainer's
own repository and some of changes are sometimes committed together to
ruby-core repository.

Matz complained about such a development style in :

| I have hated the development process in that some maintainers develop
| their libraries in their own repository and commit together into ruby-
| core repository. For example, I hear that _why has some uncommitted
| updates of Syck in his own repository. And, REXML.
|
| It's OK for maintainers to have their own repository because of the
| age of distributed VCS. But it should be synchronized with ruby-core
| repository bi-directionally. Some problems actually occur.

I completely agree with matz. The HEAD of all standard libraries should
be put in core repository.

This ticket is registered as [BUG] because this is a bug of the development
process.

--
Yusuke ENDOH mame@tsg.ne.jp
=end


Related issues

Related to ruby-trunk - Bug #2066: Merge Latest RDoc/Ri Closed 09/09/2009

History

#1 Updated by Yui NARUSE over 4 years ago

  • Status changed from Open to Assigned
  • Assignee set to Eric Hodel

=begin
We suffered from both not updated gems and many test-all fails after huge merge.
(and degrades by reverting Ruby 1.9 local changes)

So I agree with this.
=end

#2 Updated by Yui NARUSE over 4 years ago

  • Priority changed from Normal to Urgent

=begin
How about this ticket?
=end

#3 Updated by Eric Hodel over 4 years ago

=begin
I can update RubyGems tomorrow, Friday at latest.

If I were to move RubyGems main development into ruby's repository I would need to make tags for RubyGems releases somewhere in ruby's repository. Would this be ok?

If moving RubyGems main development into ruby's repository is desired, should another ticket be opened? There may be other issues to consider since RubyGems still needs to make regular releases.
=end

#4 Updated by Eric Hodel about 4 years ago

  • Status changed from Assigned to Closed

=begin
Nobu updated RubyGems to 1.3.6 for me.
=end

Also available in: Atom PDF