> Eggs are one of the great things about Chicken, but the inverse > argument is that as people upgrade to 4.0.0 they'll port the eggs they > need and evolve the new version's support. That said, I think a way > to select between the two would be the optimal solution. One option > is to try to get both running side-by-side (we'd have to hack some > stuff of course since they both like to install files with the same > name e.g. "csi" and "csc" but we already have to do that to get > versioned libraries). Here's a tarball with a completely fixed (paths, shared libraries, etc.) port for chicken 3.4.0. I know it should be a patch, but I'm blanking on how to include the added patches in the cvs diff. cvs add isn't marking them for inclusion. (Too much time with git and mercurial, I guess.) I'll look into it more tomorrow, and once that's up, I'll work on a multi-version port.
scott
chicken-3.4.0-port.tgz
Description: GNU Zip compressed data
