From: Massimiliano Mirra <list@...>
Date: 2002-08-28T05:27:07+09:00
Subject: Re: Ruby developers: help push RPKG development and usage forward!! (it is like CPAN.pm, only Ruby)

[Resending this as it showed up on ruby-talk.org but neither on the
newsgroup nor on the list.  Apologies if this is a duplicate for you.]


I'm joining the thread here because I cannot find the initial part in
my mailbox (I read it on ruby-talk.org though).

I'm rpkg author.  I'm rewriting it from scratch, including many sweet
things based on advice from Sean Russel and others.

Right now you can do something like this:

rpkg pack --meta http://site.com/foo-0.1.src.dsc

The .dsc file looks roughly like this (non relevant parts omitted):

Package: foo
Version: 0.1
Files:
 a9s5b2erf024eht9323 cvs://cvs.somewhere.com/foo#Release_0_1
 fm1313n90404hngh043 rpkg://build/foo-0.1.mkr.tar.gz

Sources will be downloaded as well as maker scripts.  Maker scripts
will be executed, things will be compiled if they need be, and one or
more distribution policy compliant packages (.rpk) will be built.
Compiled .rpk's can then be redistributed. A maker script can be in
any language and for me rarely has gone beyond a dozen lines of bash
script.

So far, you can get stuff from cvs://, http://, file:// (i.e. the
local filesystem), rpkg:// (any of the rpkg mirrors specified in a
config file).  Planned rsync and ftp.

It's easy to see how maker scripts being separated from upstream
tarballs calls for a very fast and easy growth of the number of
available packages.

What remains has to do with database management and dependency
handling.  Its coming to light is constrained by my available time,
which right now is little.  Anybody would like to help?  I'll make
the
new rpkg available if anyone is interested.


Massimiliano