I can't freaking believe we're going to go another cycle with a broken Rubygems. The sad thing is that Ruby has a very creative and productive developer community that is staying on or moving to MacOS because it's so easy to get into Linux-y Ruby development there. Rubygems comes with Leopard! Apple is actively targeting Ruby and Python open source developers.
One misunderstanding about Rubygems in these reports is that Rubygems is *not* used for system scripts (I mean, as a rule). It's used to keep track of extremely quick-moving distributed development that's pulled together for web applications (again, as a rule). Nobody would ever dream of using a gem as a requirement in a Deb package. They would do the right thing and package up the library for Apt. That's not the issue here. Rubygems is a tool for keeping pace with the world of Ruby development, which proceeds much faster than a distro packaging process. One horrible irony in all this is that at least until recently the most recent source package for Rubygems is actually broken on Ubuntu systems. You have to manually edit a file to include a require statement presumably because of a difference in the Ruby Debian package from the standard upstream distribution. This is what a Deb package is supposed to do, work out all the little details and even take up slack for the upstream developers. Instead we get this. I'm pretty sure it loses users. -- rubygems bin in PATH potentially breaks other applications and violates all sense of decency in packaging. https://bugs.launchpad.net/bugs/262063 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
