Project

General

Profile

Actions

Bug #2355

closed

Please update rubygems!

Added by mame (Yusuke Endoh) about 15 years ago. Updated over 13 years ago.

Status:
Closed
Target version:
ruby -v:
ruby 1.9.2dev (2009-11-11 trunk 25717) [i686-linux]
Backport:
[ruby-core:26679]

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 [ruby-dev:39373]:

| 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
=end


Related issues 1 (0 open1 closed)

Related to Ruby master - Bug #2066: Merge Latest RDoc/RiCloseddrbrain (Eric Hodel)09/09/2009Actions
Actions #1

Updated by naruse (Yui NARUSE) about 15 years ago

  • Status changed from Open to Assigned
  • Assignee set to drbrain (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

Actions #2

Updated by naruse (Yui NARUSE) almost 15 years ago

  • Priority changed from Normal to 6

=begin
How about this ticket?
=end

Actions #3

Updated by drbrain (Eric Hodel) almost 15 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

Actions #4

Updated by drbrain (Eric Hodel) over 14 years ago

  • Status changed from Assigned to Closed

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

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0