On Fri, Feb 22, 2008 at 02:38:25AM -0800, Alejandro Forero Cuervo wrote: > So what about the idea of adding a (supported-releases 2.3 3.0.0) tag > to the meta file, where particular versions of an egg that needs to do > so specify which is the range of Chicken releases it supports?
Actually, this is a much better idea as it also provides better granularity than the current system. I have a practical problem *right now* with my soon-to-be-released wmiirc egg. It _requires_ chicken 3.0.1 (because of a change in the way printf works on ports), but I can't currently express this in the meta file/repos tree, afaik. So it's located in the release/3 but it won't actually work with the 3.0.0 release. Cheers, Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth
pgpJLy2Uv5EvH.pgp
Description: PGP signature
_______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
