David Vallner wrote:
> Jamey Cribbs wrote:
>> Pieter Kubben wrote:
>>> Preferably relatively easy to distribute.
>>>
>> Whichever you choose, be sure to use RubyScript2Exe to package
>> everything up into one easy to distribute executable.
>>
> 
> I'd advise to use distribution-specific packaging for Linuxen. I get
> twitchy when I have to install an app that APT won't know about.
> 
> David Vallner
> 
> 
Which means you need at least a .deb and .rpm binary package, Debian
source and RPM source, a pure source tarball for everyone else and a
friend in the Gentoo community to make you an ebuild from the tarball.
:) Makes gem look better and better with each word I type. :)

Seriously, though, since I run Gentoo, I have similar problems. Gentoo
has its own repository, and quite a few of the more popular gems are
already packaged. Rails, rake, gem itself, of course, nitro, fxruby,
qtruby, etc. are all in Gentoo.

But if there's a gem I want that isn't in the Gentoo Portage tree, I can
install it. Portage doesn't know it's there. I install source tarballs
all the time; they usually go into /usr/local by default, which keeps
them out of the way of the main distro which puts everything in /usr by
default.