It would be very handy the addition of a cli command (eg. zip/export) which exports a revision to a zip file, similar to the wiki feature. This is handy when a graphical browser is not available (eg. console only environment).<br>
Thanks

<hr><i>anonymous claiming to be dlane added on 2010-03-03 16:29:51:</i><br>
A workaround which works currently could be 

<verbatim>
$ curl "http://www.fossil-scm.org/fossil/zip/Fossil-71edacd95f.zip?uuid=71edacd95f" > 71edacd95f.zip
</verbatim>

Fossil generally treats urls sanely and changes them slowly. It generally allows unique prefixes for artifacts: the browser url has a longer value for uuid but it turns out to be enough to replicate the shorter prefix that is available, for example in

<verbatim>
$ fossil finfo <filename>
</verbatim>

The perl/python/ruby/tcl(?) to bind these conveniently should not be very hard.
Tags etc left as a Simple Exercise for the Reader.

<hr><i>ron added on 2010-03-03 18:55:16:</i><br>
Actually, on Linux do "fossil set web-browser lynx".  Then when you do "fossil ui", you will get the console 'lynx' browser (substitute some other browser if you like).  This works nicely, I was able to get the zip this way without using Firefox etc.

<hr><i>anonymous claiming to be Ross Berteig added on 2010-03-11 03:21:19:</i><br>
I just posted a patch to zip.c to the mailing list to implement a fossil zip command that understands a uuid (or prefix) or tag and creates a zip file that is identical to the one created by the web ui.

The existing fossil test-baseline-zip command produces archives that are very similar, but use a different name of the top level folder in the zip. And its undocumented.