Re: [Chicken-hackers] multiple issues in embedded PCRE

[Mario Domenech Goulart]

Hi Matthew and folks,

On Fri, 23 Nov 2007 13:20:08 -0700 Matthew Welland <address@hidden> wrote:

> On Friday 23 November 2007 06:03:15 am Peter Bex wrote:
> > On Fri, Nov 23, 2007 at 12:44:16PM +0100, felix winkelmann wrote:
> > > On Nov 23, 2007 6:19 AM, John Cowan <address@hidden> wrote:
> > > > Fair enough.  Since the tarballs don't come with eggs (there is only
> > > > one egg repository), in effect you have the best hope of using
> > > > eggs if you have the trunk code replaced.  To have what other
> > > > projects mean by stable releases, we'd have to branch the
> > > > egg repository with each release and make sure that chicken-setup
> > > > from a tarball invokes the correct set of eggs.  That way you
> > > > could load 2.731 and get the 2.731-usable eggs with it.
> > >
> > > I lord... Even though I feel that this is the only really working
> > > solution, the amount of storage, bandwidth and the added complexity for
> > > the tools makes my head spin...
> >
> > I don't think the tools need to be changed.  You just need to point
> > chicken-setup at a specific version of the egg tarball repository and
> > it defaults to the one that matches the version, I think.
> 
> This doesn't seem that hard from my (posibly naive) perspective. 
> 
> In every release an "svn cp .../eggs .../rel-a.b.c/eggs" is done. 
> chicken-setup merely needs to a) know the version and b) get the eggs 
> from .../rel-a.b.c/eggs

That would be a good approach.  However, the chicken-setup part is not
so simple.  chicken-setup fetches eggs using HTTP from
www.call-with-current-continuation.org.  The svn repository is hosted
at chicken.wiki.br; eggs are uploaded to call/cc.org preiodically.

So, it seems to me that there are two main alternatives:

1. uploading multiple versions of eggs to call/cc.org (I don't know
   its disk space restrictions).  chicken.wiki.br's machine (aka
   galinha) is available for making eggs available, of course (and for
   whatever chicken-related job), in case disk space on call/cc.org is
   a problem.

2. make chicken-setup act as an svn client to access the eggs
   repository directly.  Don't know how difficult it would be.

Best wishes,
Mario