If you’re a Ruby author who cares about distributing your software to more than just other programmers’ laptops, you only need to take some simple action with your existing Gems to make them compatible that the Debian folk wrote years ago. I’d add the following to these tips though:
1. don’t use the gem command in your main code at all, use a loader program that pulls it in if you need it. In almost all cases it is going away in 1.9, and good riddance;
2. if you provide a Ruby library called foobar, make sure your gem is also called foobar, and preferably only provides a single module called Foobar;
3. don’t use capital letters in your gem name - amazingly there are already some gems in the namespace that differ only by case!
Bytemark blog | Ruby gems, and when we’ll be shot of them