chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: felix winkelmann
Subject: Re: ***SPAM*** Re: [Chicken-hackers] multiple issues in embedded PCRE
Date: Fri, 23 Nov 2007 12:44:16 +0100

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...

Is this a viable approach? What do others think? How could one keep
track of bugfixes merged from one branch to the other? Is svn flexible
enough for this? Any opinions?


cheers,
felix




reply via email to

[Prev in Thread] Current Thread [Next in Thread]