New asdf version

Behaviour of the :force operation option has changed, in light of
lessons learnt dealing with clx, clim and closure, all of which take
ages to rebuild -

:force :all   => rebuild everything including depended-on systems
:force t      => rebuild only the current system
:force (system1 system2 ...) => rebuild the named systems

This also has support for the experimental HYPERDOCUMENTATION
protocol, which allows ASDF Systems to specify where their reference
documentation is in a standard manner.  Your feedback on this is
solicited.  

http://www.cliki.net/ASDF%20System#documentation for the general idea,
and here's a sample usage -

(in-package :sb-bsd-sockets)
(defmethod asdf:hyperdocumentation ((package (eql #.*package*)) (thing symbol) type)
  (declare (ignore type))
  (format nil "file://~a#~A"
	  (namestring
	   #.(merge-pathnames
	      "index.html" (or *compile-file-pathname* *load-pathname*)))
	  thing))

* (asdf:hyperdoc 'sb-bsd-sockets:inet-socket t)
"file:///home/dan/src/sourceforge/thread-sbcl/sbcl/contrib/sb-bsd-sockets/index.html#INET-SOCKET"

I think something like this would be a useful feature for ILISP and
similar environments: now you don't _just_ have online hyperspec
lookups, you can lookup docs for any package you have installed.

On a related note, I'm also thinking about saying that "ASDF Systems"
should implement a test-op, which does regression testing of some form
(again, leaving it up to the user to decide how exactly).  This
doesn't affect anyone who doesn't want to be affected by it (your .asd
file doesn't have to conform to the "ASDF System"(tm) requirements) 
but opinions are sought from vn-cclan people there.
 

-dan

-- 

   http://www.cliki.net/ - Link farm for free CL-on-Unix resources 


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en