4 ms·

I'd like to hear more about what is being done on the packaging front, specifically Rubygems v Debian. Last I heard, the Debian folks weren't too happy with Ru

I'd like to hear more about what is being done on the packaging front, specifically Rubygems v Debian. Last I heard, the Debian folks weren't too happy with RubyGems because people who install RubyGems can upgrade gem dependencies without updating dpkg resulting in an inconsistent state. IIRC there was effort underway to bring RubyGems and all of it's gems into the dpkg repository.

sandal 15y ago
The Debian situation has always seemed a bit unreasonable to me because RubyGems is designed to be a tool for Rubyists, not sysadmins. The overhead of doing operating system level integration to respect various package systems and the way they work would be way too much for the RubyGems team. However, if changes need to be made to allow third party packagers (such as Debian) to use RubyGems in the way they want, those issues should be revisited. It's not reasonable to expect RubyGems to change its core focus or support lots of Debian specific functionality, but it is reasonable to think that if all that is needed is some extension points or something like that, the issues should be dealt with. Please ask the Debian folks to file tickets against RubyGems, or to re-raise discussions on the rubygems-developers mailing list.