So, creek is nearing enough maturity to be released on an unsuspecting world. I've been thinking on (a) what more I want and (b) what's the minimal extras needed.

• License (provisionally, MIT-licensed)
• Client library for C
• Client library for Lisp
• Client library for Perl
• client library for Python (DONE, I think)
• Better documentation
• Built-in support for submaps
• Map visualization
• ACL "editor"
• ACL "dumper"

Combined with this is some slight worries regarding packaging. I was hoping that the Python "disutils" package would allow me to auto-build tar files in the form and shape I wanted, but it seems as if the "sdist" option only picks up the source and leaves other things out. I guess I could do ad-hoc packaging (after all, that's almost what I do when I release CL packages, build-asdf-package is a bit too ad-hoc and requires at least one manual step; I've been considering routes around that, though, introspecting into the ASDF data, but so far nothing stable-enough has gelled).

Harking back to submaps... At the moment, it's sort-of doable (set up a split/join, with one split transit heading straight to the join, the other pointing at "the submap" and have the submap end up with a destructor AND run a separate daemon to go through the item inventory and push through any item that resides only in a join). This is all cumbersome and ugly, but...

To fix it would require two new state types (submap-split and submap-destruct) and possibly a third (submap-join). It would also need another database table (essentially a "submap stack"). But, darn, I can see it coming in handy.

Ah, well. Another day.