Please update rubygems!
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
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
Yusuke ENDOH email@example.com
#3 Updated by Eric Hodel over 6 years ago
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.