Comment 24 for bug 307462

Your right, that last quip was uncalled for.

I do want a good solution, however, it seems the ruby & debian community are often at odds. I somewhat understand why it is so difficult to reconcile.

Ruby uses rubygems, which work great btw. Ruby has lots of different types of packages and versions. Things in Ruby move fast and debian is all about stability. The culture and processes are vastly different. What I meant by "trusting Phusion more", is Phusion part of the Ruby culture and thus more compatible with most Ruby development. I don't want to be locked into the debian world when it comes to Ruby. Everything else, I'm happy to be in the debian world.

The thing I'm worried about is that I do not use the ubuntu/debian ruby stack at all, because it simply does not do what I want it to do. I can't use it. I'm sorry, but that is the truth. I think that a number of other developers agree with me too.

Using the REE package is not a slight for the maintainers of the Ruby package. MRI is slow, and REE fixes some of the slowness. I just wanted to share because others may want a faster version of Ruby that is .deb packaged.

This probably is the wrong forum for this discussion. I'm happy to take it elsewhere if you wish to continue.

Maybe RVM (Ruby version manager) will be a good solution. You can have a RVM package using the ruby with --enable-pthreads to keep compatibility with tk, and have a streamlined version of ruby (no pthreads MRI or REE) for general development. Maybe a rule that the number of packages that depend on the streamlined version of ruby should be limited?