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

[Mario Domenech Goulart]

On Fri, 23 Nov 2007 00:19:44 -0500 John Cowan <address@hidden> wrote:

> Mario Domenech Goulart scripsit:
> 
> > Anyway, maybe that's just a slightly different view of the "stable"
> > word.  The fact is that we have a release tarball (supposedly "bug
> > free"; given a version number, the code doesn't change and it doesn't
> > need chicken to be compiled) and the svn branches code (development
> > code, constantly changing and needs chicken to be bootstrapped).
> 
> 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.

Nowadays, as far as I can see, the eggs are informally
"release-oriented", that is, egg authors tend to keep their eggs
working for the latest release.

The current trunk situation kind of illustrates this fact.  Several
eggs which work with the current release don't work with chicken from
trunk (because of procedures/macros that have been removed), but it is
not considered a serious issue because trunk code means development
code.  The opposite (i.e., eggs that work with trunk but not with the
release) is quite rare and people usually complain when it happens.

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

Yeah, that would be the ideal situation.

PS: sorry for the "*** SPAM ***" tag on the previous message.  It was
automatically inserted by the anti-spam software (which is pretty dumb
sometimes).

Best wishes,
Mario