On 29 Mar 2009, at 9:12 pm, Shawn Rutledge 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.
The best thing we can do is to identify when somebody's using chicken
3 purely due to egg support rather than any better reason, and try to
port all the eggs they use; we can leave eggs behind, if nobody uses
them - it can be good to cut away dead wood once in a while...
But, yes, we'll also have to deal with the fact that lots of things
will be stuck on chicken 3 just because that's how package systems
work. So the chicken 3 infrastructure will need to keep working for a
while.
ABS
--
Alaric Snell-Pym
Work: http://www.snell-systems.co.uk/
Play: http://www.snell-pym.org.uk/alaric/
Blog: http://www.snell-pym.org.uk/?author=4
_______________________________________________
Chicken-hackers mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/chicken-hackers