*** :maintainer (...)

A list of "name <place>" (where place is an email or irc or forum url or whatever)
Contact info for maintenance issues.

*** :docpath relative-path

*** :tags (...)

Each package may also be marked by a list of tag keywords.  Users can specify these when selecting what to install.  Here are the initial tags.

:core - a "core" LibCL package
:doc - a documentation tool
:graphics - image loading, saving, and manipulation
:util - simple utility functions (i.e. general-purpose tools)
:ffi - this package relies on ffi (non-lisp) bindings
:reader - tools for modifying the lisp reader
:test - testing frameworks
...

*** :todo notes

Things that should probably happen before the release.


*** :version "version"

Indicate the version number if this was a tagged release.
Sometimes a simple bugfix appears after a tagged release.
Need a suffix to mark when these minor changes are being used.

*** :date "YYY-MM-DD"

Indicate the date of the release or snapshot.

*** :source (...)

The darcs hash may rely on darcs2.  It can be obtained by a variant of the following incantation.
# darcs changes --last 1 --xml-output | grep hash= | sed -e "s/.*hash='\(.*\)'.*/\1/"

Many of Edi's libraries can be found by running
# svn propget -R svn:externals svn://bknr.net/svn/ediware

Known source types
(:cvs url module revision-specifier) ; cvs revs are often specified as "-D 2010-12-34" to get all the commits on 2010-12-33...
(:darcs url hash)
(:git url sha1-hash)
(:svn url revision)
(:wget url filename) ; so #mv filename $canonicalname # or need more?