Chapter 2.20 --- Extra Credit

Packaging Lisp Libraries

"A 'critic' is a man who creates nothing and thereby feels qualified to judge the work of creative men. There is logic in this; he is unbiased---he hates all creative people equally."

Now that you've got a solid grounding in writing, optimizing, debugging and testing your Lisp software, it's time to learn all about packaging your code for the wild---namely with ASDF, to be distributed in the Quicklisp package manager. You've been using ASDF system files and Quicklisp to manage your projects since Part One, but now it's time to take a closer look at the structure of these ASDF files, and all the awesome power they can hold.

But, as the famous saying goes, with great power comes great responsibility---there's a right way of packaging your libraries, and there are certain limitations as to what sort of project qualifies for inclusion in Quicklisp. We'll be covering all this and more.

Exercise 2.20.1

Considerations for a Useful Library

Exercise 2.20.2

Quicklisp Library Submission Guidelines

Exercise 2.20.3

Required System Metadata

Exercise 2.20.4

ASDF In More Detail

Exercise 2.20.5

System Dependencies

Exercise 2.20.6

More System Dependencies

Exercise 2.20.7

Components: Files and Modules

Exercise 2.20.8

Component Interdependency

Exercise 2.20.9

Multiple Systems and Packages

Exercise 2.20.10

Test Suites

Exercise 2.20.11

More Test Suites: FiveAM

Exercise 2.20.12

More Test Suites: Prove

Exercise 2.20.13

Continuous Integration Testing

Exercise 2.20.14

Code Coverage Testing