New projects: big-string, cl-css, cl-curlex, cl-enchant, cl-geoip, cl-performance-tuning-helper, cl-tcod, cl-template, clache, clinch, clite, clobber, delorean, generators, gettext, inner-conditional, lowlight, new-op, petit.package-utils, policy-cond, pretty-function, rectangle-packing, stmx, track-best, treedb, utilities.print-items, weblocks-stores, weblocks-utils.
Updated projects: 3bmd, antik, array-operations, asdf-finalizers, asdf-project-helper, backports, binary-types, bordeaux-threads, buildnode, cffi, chronicity, cl-6502, cl-algebraic-data-type, cl-async, cl-async-future, cl-cairo2, cl-data-format-validation, cl-dbi, cl-decimals, cl-dot, cl-freetype2, cl-general-accumulator, cl-geocode, cl-glfw, cl-gss, cl-html5-parser, cl-iconv, cl-libxml2, cl-murmurhash, cl-num-utils, cl-openal, cl-prime-maker, cl-protobufs, cl-quakeinfo, cl-rrt, cl-seek-project, cl-selenium, cl-skip-list, cl-slice, cl-tulip-graph, clack, clfswm, closer-mop, clpython, clsql-orm, coleslaw, colorize, com.informatimago, commonqt, css-selectors, dartsclhashtree, defmacro-enhance, djula, doplus, dynamic-collect, fare-mop, fare-utils, fiveam, gbbopen, gendl, gsll, http-parse, hu.dwim.delico, hu.dwim.util, hu.dwim.walker, hunchentoot, intercom, lisp-gflags, lisp-interface-library, lisp-unit, lla, local-time, log4cl, lparallel, make-hash, message-oo, mime4cl, montezuma, more-conditions, mtlisp, optima, pzmq, query-fs, rfc2109, romreader, sclf, sip-hash, slime, spinneret, stp-query, stringprep, toadstool, uiop, weblocks, yaclanapht.
To get this update, use (ql:update-dist "quicklisp").
If this update breaks any of your software, see Going back in (dist) time.
This is a seriously impressive project, but I'm having an issue with discoverability. Is there a single list anywhere of what the projects actually are? Not just their names and dependencies (which, sure, I could just Google) but an actual catalogue with a description of each one? I've checked the various pages and haven't found one yet.ReplyDelete
There's no good solution for that right now, sorry. I use google + the name of the project + the word "lisp" to find info.Delete
Actually, give http://quickdocs.org/ a try, too. A search for "XML" gives nice info, for example.Delete
I always keep a tab open at http://cliki.net, and use it whenever I need some new library. It comes with a list of (currently) recommended libraries, which is good for starters, and you can browse projects by category or search by keyword/name.Delete
This bothers me a lot as well.. Is there at least a support (or plan) for "short descriptions" or some tags in Quicklisp? I think if that would become a part of package information, then it could be extracted as well.Delete
The releases page at http://www.quicklisp.org/beta/releases.html is auto-generated from a database of some sort, presumably. Could you generate a separate one, the DIY Documentation Page, that wraps every project "foo" in some html like [a href="https://www.google.com/#q="foo"+lisp]foo[/a] so that people could google stuff easily? It's not a solution, but it would help...ReplyDelete
PS Did I mention "seriously impressive"? Just in case you think I'm teaching grandma to suck eggs, or indeed teaching the world-famous quadruple-Olympic-gold-medal-winning internationally renowned egg-sucking expert who has just been awarded the Noble Prize for Egg-Sucking... to suck eggs. If you see what I mean. That would be more like it.Delete
The "database of some sort" is available to public, so you can generate this page yourself.Delete
(mapcar #'ql-dist:name (ql-dist:provided-releases (ql-dist:dist "quicklisp")))
=> list of project names
This comment has been removed by the author.ReplyDelete
For CLISP on Windows, I get an error on the first updated project, "xml.location.20130312-git" as follows:ReplyDelete
PARSE-NAMESTRING: syntax error in filename "dists/quicklisp/software/xml.location-20130312-git/xml>.location.asd" at position 54
There seems to be an "xml>." in the file pathname.
Do you also use Clozure CL?Delete
There's an issue I need to fix when writing out data from CCL and reading it in with other implementations. CCL escapes #\.s in pathname components with #\>.
A temporary fix is to zap your ~/quicklisp/dists/quicklisp/installed folder.
Thanks, Xach. I do indeed also use CCL, so that would have to be the reason. I will try your suggested workaround at the next opportunity.Delete