New projects: city-hash, cl-dbi, cl-gdata, cl-portaudio, cl-variates, clesh, clhs, dlist, monkeylib-json, monkeylib-parser, napa-fft3, parseltongue, persistent-tables, random-access-lists, shadchen, swank-client, toadstool, trivial-dump-core.
Updated projects: alexandria, babel, blackthorn-engine, blackthorn-engine-3d, caveman, chipz, cl-2d, cl-azure, cl-cairo2, cl-csv, cl-decimals, cl-dropbox, cl-enumeration, cl-i18n, cl-libxml2, cl-llvm, cl-mongo, cl-mssql, cl-murmurhash, cl-mysql, cl-num-utils, cl-oauth, cl-project, cl-random, cl-redis, cl-scribd, cl-twitter, cl-unification, cl-yahoo-finance, clack, clazy, clfswm, closer-mop, collectors, com.informatimago, com.informatimago.rdp, css-lite, drakma, ext-blog, gbbopen, gtfl, gtk-cffi, ht-simple-ajax, hu.dwim.util, js, latex-table, lift, linedit, lisp-on-lines, lla, lparallel, manifest, metabang-bind, metatilities-base, misc-extensions, mixalot, monkeylib-markup, monkeylib-markup-html, monkeylib-pathnames, monkeylib-prose-diff, monkeylib-utilities, parenscript, perfpiece, png-read, priority-queue, protobuf, quickproject, rutils, shuffletron, slime, toot, yason, zs3.
Removed projects: monkeylib-foo.
Weblocks does not compile right now.ReplyDelete
Xach, first of all, thanks for quicklisp. It's fantastic.ReplyDelete
Second, about Weblocks, there was a recent patch that supposedly gets it working with hunchentoot 1.2.x. Is that still broken? If we have the weblocks source directory, can we quickload it from the local source tree to have quicklisp get the dependencies automatically (like vectoot in your youtube demo)? I am looking forward to getting weblocks working.
Third, a feature request: I often want to find out some information about a system before loading. It usually works to google the system name give or take, but it would be nice if some basic metadata could be accessed, when it is available, through quicklisp, such as a brief description, last update time/version, and a web page. Perhaps a standard metadata file (e.g., README or info.txt) could be included (optionally) for each system in the repository and scanned by, say, ql:system-info. Just a thought.
In any case, thanks again for this.
Weblocks was updated for hunchentoot but ran into another small problem with Parenscript. It has been fixed in git and the next Quicklisp release in March should have Weblocks back in. In the interim if you clone git://github.com/skypher/weblocks.git in ~/quicklisp/local-projects/ you should be able to quickload weblocks with all dependencies fetched automatically.ReplyDelete
I really want to provide information about projects up front but I'm still working on the best way to do it. I agree it's important to know what e.g. "snoodlepond" might be before trying to load it.
Terrific, thanks Xach.ReplyDelete
That snoodlepond *is* a great package, I must say.