On Thu, Jan 24, 2013 at 4:19 PM, Moritz Heidkamp <[email protected]> wrote: >> I've put up docs on the wiki: >> https://wiki.call-cc.org/eggref/4/redis > > You mention "Note that you will need to fetch the git submodules in this > package." -- I wonder if the .tar.gz includes the checked out > submodules, too? Otherwise it won't work with the eggs infrastructure > I'm afraid. We'll know in a bit though :-)
It includes the submodules. The release-info file points to a tarball on my website that's automatically generated from the github tags. >> Could someone make this accessible via chicken-install? Thanks! > > Done! Thanks! >> I'd also appreciate if someone had a look at the >> meta/release-info/setup files and let me know if I'm doing something >> inappropriate. > > Looks fine AFAICS. You can remove the `egg', `files' and `doc-from-wiki' > clauses from the meta file, though. They are not needed anymore. I'll remove them. Thanks for having a look. > FYI, I also made a Redis egg once which I never released because I > didn't need it eventually and then I couldn't be bothered to finish it > up and write documentation for it :-) I took a slightly different > approach in providing a high-level API which exposes each Redis command > as a Scheme function. You can find the code here > https://gitorious.org/chicken-eggs/redis Ah, this egg was born because I needed something really quickly once I hit a performance bottleneck with redis-chicken, hence the basic API. Andrei _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
