@Xach:folio needs a new fixes to reduce its quicklisp-hostility. Most notably, I should (and soon will) remove FSet from folio and rely upon the fact that Quicklisp provides Fset for me.

Why was Fset included in folio to begin with? Because folio depends intimately on FSet, and I have always found it really annoying to have to hunt all over the net for some number of dependencies in order to try out some library. But Quicklisp does a good job of solving that problem for me, so I'm inclined to stop including dependencies in my libraries.

There's some sort of positive feedback there, too: it makes packages that are already in Quicklisp significantly more attractive as dependencies than ones that are not.

@MCAndre:Just put :depends-on :foo in your asdf system definition when you want to use Foo. When you asdf-load your system, if Fo is not present, asdf will complain. Then you can do (ql:quickload "foo") just that one time. On future loads (as long as your Lisp's init file loads quicklisp), asdf will automagically find Foo for you.

Maybe there is room for some simple utility that one can use to load ones project with ASDF, and that catches missing dependencies and attempts to automagically quickload them?