Re: [Chicken-hackers] manual and chicken4 infrastructure

[Ivan Raikov]

Hello,

  As Elf pointed out, the 3.5.0 release was botched because too many
untested modifications were made to it. The current development
snapshot, 3.5.5 includes bug fixes for some of those issues, although
I am not convinced of the stability of srfi-18, and someone reported a
segmentation fault while building Chicken 3.4+ on x86_64
architecture. So 3.4.0 should be considered the last "stable" release
of the 3.x series, and the 3.5.x development snapshots will be used
for backporting features from 4.x until enough eggs are ported so that
we can retire the 3 branch altogether.

  As for why the 4.0.0 release was not on the releases page, the
excuse is that some infrastructure has to be updated on the Chicken
wiki server before 4.x tarballs can be generated automatically. The
main Chicken page does have a link to the 4.0.0 release tarball. I
have also added a link to it on the releases page, and I will post an
announcement on Freshmeat shortly.

   -Ivan


Shawn Rutledge <address@hidden> writes:

> The main page points to
>
> http://chicken.wiki.br/releases/
>
> 3.4.0 is there.  So it gives the impression that's the newest "stable"
> version.  Now I wonder if that's actually true?  There are more dev
> releases in the 3.4.x series; which one should Linux distros be using?
>
> 4.0.0 is NOT there.
>
> Why can't the releases page actually be in sync with the releases that
> are available?  Because it's a manual process and somebody always
> forgets to update it?  Maybe make it more automated then?  or just
> point to a web directory which has listings turned on and does not
> have an index file, so we can see what tarballs are there.
>
> On gentoo I managed to build 3.4.0 by just copying the 3.3.0 ebuild.
>
> I haven't seen a link anywhere to
>
> http://www.call-with-current-continuation.org/chicken-4.0.0.tar.gz
>
> other than Felix's email.  Why isn't that in the usual releases
> directory instead?
>