[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] manual and chicken4 infrastructure
From: |
felix winkelmann |
Subject: |
Re: [Chicken-hackers] manual and chicken4 infrastructure |
Date: |
Mon, 6 Apr 2009 00:38:32 +0200 |
On Sun, Mar 29, 2009 at 10:12 PM, Shawn Rutledge
<address@hidden> wrote:
>
> Ideally no eggs would be left behind, but maybe that's not realistic.
> Some other projects end up maintaining both new and old branches for
> years for that kind of reason. (KDE 3, Qt 3, ReiserFS V3, perl 5,
> BlueZ 2 and 3, ...) And Linux distros will tend to lag behind for a
> long time, too. E.g. I have to work on OpenEmbedded one of these
> days, and I imagine Gentoo won't get Chicken 4 for quite a while
> either.
The eggs for chicken-3 will remain, but it doesn't make sense to port
all of the chicken-3 eggs to chicken-4. Some of them simply will
not work because they use old internal code (codewalk, for example).
And some eggs are probably obsolete.
cheers,
felix
- Re: [Chicken-hackers] manual and chicken4 infrastructure,
felix winkelmann <=
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Peter Bex, 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Marijn Schouten (hkBst), 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Shawn Rutledge, 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Elf, 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Marijn Schouten (hkBst), 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Elf, 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Shawn Rutledge, 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, Ivan Raikov, 2009/04/06
- Re: [Chicken-hackers] manual and chicken4 infrastructure, felix winkelmann, 2009/04/07