From: Kevin Brown <blargity@...>
Date: 2005-10-03T02:17:13+09:00
Subject: Re: why can't Ruby load .gem files directly?

On Sunday 02 October 2005 11:06, Joshua Haberman wrote:
> On Oct 2, 2005, at 9:10 AM, Eivind Eklund wrote:
> [*snip*]
> May I request that we talk about technical issues like grown-up
> engineers, not like guests on "Jerry Springer?"

Unnecessary insult, but sure.

> Tell me if this is an accurate list of the problems packaging gems:
>
> 1. Gems provide more guarantees than Debian packages can

Gems provide guarantees that turn out to be wrong with the way Debian installs 
software with its packaging scheme (out of the way of the user, so that you 
can install your own stuff in /usr/bin etc).

> 2. Gems let you install more than one version of the same software,
> but Debian packages don't

Debian packages do, but will maintain a symlink to the most recently installed 
version.  I have python2.2 and 2.4 installed right now, but the symlink 
points to 2.4, thus causing problems if python2.2 software assumes it can get 
to python with /usr/bin/python.

> 3. something about Debian wanting software to be in a single directory?

Not quite, but in an out of the way place.

> I've tried to bring myself up to speed on these issues by reading
> recent threads, but it's very difficult to separate the technical
> information from the arguing.

Hope I've helped.

> Josh