Hi, We (Akira, Daigo, I) had an email discussion about to best package Rubygems (the software, not the gems packages). Now that Ruby1.9 includes Rubygems, we have a problem, because that meant that we have to maintain two seperate rubygems versions (one for ruby1.8, in the rubygems source package, using the version on www.rubygems.org, and one for ruby1.9, in the ruby1.9 source package).
We decided that, instead, we will drop rubygems from the ruby1.9 source package, and generate two versions (one for 1.8, one for 1.9) in the rubygems source package. This has several advantages: - Users get a newer rubygems version, even on Ruby1.9 - Bugs all go to the same source package - Patches don't have to be kept in sync between two source packages As a side note, the binary packages will be renamed, so that we only keep: - rubygems1.8 for Ruby1.8 - rubygems1.9 for Ruby1.9 I think that this makes more sense than using libgems-ruby1.X, since rubygems is more an application than a library. Any comments? -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | _______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
