[DRE-maint] (no subject)

[Lucas Nussbaum]

debian-ruby at lists.debian.org
Bcc: 
Subject: Re: [DRE-maint]  Rubygems
Reply-To: 
In-Reply-To: <245fb4700907280223j12280241k168056dca8a56422 at mail.gmail.com>

On 28/07/09 at 02:23 -0700, Yehuda Katz wrote:
> On Tue, Jul 28, 2009 at 2:01 AM, Lucas Nussbaum <lucas at lucas-nussbaum.net>wrote:
> > (Added a Cc on debian-ruby at lists.debian.org, some interested people
> > might not be subscribed to pkg-ruby-maintainers)
> >
> > Hi,
> >
> > First, thank you for contacting us on that topic.
> >
> > On 28/07/09 at 00:56 -0700, Yehuda Katz wrote:
> > > Hey guys,
> > > I recently read your position on Rubygems. I think we can probably find a
> > > way to solve the problem if we can get some help from Debian.
> > >
> > > It seems to me like you have the following problems:
> > >
> > > 1) People have libraries that rely on Rubygems. I agree with this issue:
> > > http://yehudakatz.com/2009/07/24/rubygems-good-practice/
> > >
> > > 2) You want a simple way to install packages without needing the full
> > > rubygems. To be honest, while you can appeal to the community to provide
> > > setup.rb, it would in fact be easier for us to provide you with a tiny
> > > subset of rubygems that can help you extract the installation information
> > > from the gem specification. You can then find the bin directories, as
> > well
> > > as instructions for installing any binary gems. This will enable you to
> > > install the parts of the gem where you want, and make it trivial to make
> > > debian packages from rubygems. I would be willing to write something that
> > > could serve as the base for a Rubygems=>Debian package converter if one
> > does
> > > not already exist.
> >
> > The point of setup.rb is that it enforces a layout that is sane. Of
> > course, the same could be achieved by looking into the gem specification
> > to extract the relevant info, as you suggested. I'm not very familiar
> > with rubygems, but I have the impression that this solution might not
> > apply to all current gems: it will still require a special organization
> > of the files inside the gem to work. Can you give an example of the
> > information from the gem spec that we will be able to use?
> 
> Would it be acceptable to have the gem's lib directory inside another
> directory? What are the exact requirements for how a gem needs to be
> installed on the system?