asdf-devel August 2009

asdf-devel@common-lisp.net

10 participants
22 discussions

[asdf-devel] ASDF features under discussion
by Gary King 19 Aug '09

19 Aug '09

For the record, we've had recent (but not definitive) discussions of: * whether or not optional parts of a system should be `nil` or unbound * version numbering * integrating ASDF and testing * ASDF and the windows symlink patch. If there are things I missed in the above list, please let me know. thanks, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 1

[asdf-devel] Announce: ASDF 1.360 (sorry for the churn)
by Gary King 19 Aug '09

19 Aug '09

I realized belatedly that CLISP wants (setf documentation)s to come after the thing that it is getting the documentation. Fixed. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Windows shortcuts
by Robert Goldman 19 Aug '09

19 Aug '09

Apparently, some time ago David Lichteblau proposed an asdf patch (which I am attaching) that would make it possible for ASDF to follow Windows shortcuts as if they were symbolic links. Does anyone know why this didn't make it into ASDF? Should we apply this patch? I'm just about to give a quick talk on ASDF, and I'm not looking forward to telling the Windows folks that it won't work that well for them.... Cheers, r

3 4

[asdf-devel] Proposed docstring patch for ASDF:TRAVERSE
by Robert Goldman 18 Aug '09

18 Aug '09

I was sketching out my explanation of the ASDF protocol and needed to explain TRAVERSE. I figured that while I was at it, I could provide a docstring for the function, since anyone who wants to extend it really needs to know what it is supposed to do and return. Best, r diff --git a/asdf.lisp b/asdf.lisp index c82c6e8..94b52f1 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -836,7 +836,12 @@ the head of the tree")) ;;; runs :before methods most->least-specific, which is back to front ;;; for our purposes. -(defgeneric traverse (operation component)) +(defgeneric traverse (operation component) + (:documentation "Generate and return a plan for performing +OPERATION on COMPONENT. The returned plan will be a list of +dotted pairs, each of which is an ASDF operation object and a +COMPONENT object, which are to be performed in order.")) + (defmethod traverse ((operation operation) (c component)) (let ((forced nil)) (labels ((%do-one-dep (required-op required-c required-v)

1 0

Re: [asdf-devel] Windows shortcuts
by Gary King 18 Aug '09

18 Aug '09

Thanks Daniel, > P.S. WinVista finally introduced "real" symlinks. If everyone > upgraded...<0002-Windows-shortcut-support.patch><0001-website- > changes-switch-to-load-system-etc.patch> Is there a good (and portable) *feature* or other mechanism to tell which version of Windows we're running on? -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

3 3

[asdf-devel] New manual patch
by Robert Goldman 17 Aug '09

17 Aug '09

I was reading over the info again before my talk, and I realized that there was no discussion of the test-op as one of the predefined operations, although it is predefined. Patch attached. diff --git a/asdf.texinfo b/asdf.texinfo index cfef5c6..761d606 100644 --- a/asdf.texinfo +++ b/asdf.texinfo @@ -558,42 +558,59 @@ If you are creating a component type, you need to implement this operation - at least, where meaningful. @end deffn -@deffn Operation test-system-version &key minimum +@deffn Operation test-op -Asks the system whether it satisfies a version requirement. +This operation should carry out a test on the specified component. ASDF +does not (currently) provide a method for returning a value from the +test-op (or any other operation), so the implementor must ensure that +executing the @code{test-op} has the side effect of printing useful +information about the tests to the CL stream @code{*standard-output*}. -The default method accepts a string, which is expected to contain of a -number of integers separated by #\. characters. The method is not -recursive. The component satisfies the version dependency if it has -the same major number as required and each of its sub-versions is -greater than or equal to the sub-version number required. +The default method for @code{test-op} does nothing, and will have to be +overridden, but invoking @code{test-op} on a component for which nothing +is defined will be a simple no-op. -@lisp -(defun version-satisfies (x y) - (labels ((bigger (x y) - (cond ((not y) t) - ((not x) nil) - ((> (car x) (car y)) t) - ((= (car x) (car y)) - (bigger (cdr x) (cdr y)))))) - (and (= (car x) (car y)) - (or (not (cdr y)) (bigger (cdr x) (cdr y)))))) -@end lisp - -If that doesn't work for your system, you can override it. I hope -you have as much fun writing the new method as @verb{|#lisp|} did -reimplementing this one. +The default dependency for @code{test-op} on a system is to require +@code{load-op} on that system. @end deffn -@deffn Operation feature-dependent-op -An instance of @code{feature-dependent-op} will ignore any components -which have a @code{features} attribute, unless the feature combination -it designates is satisfied by @code{*features*}. This operation is -not intended to be instantiated directly, but other operations may -inherit from it. +@c @deffn Operation test-system-version &key minimum -@end deffn +@c Asks the system whether it satisfies a version requirement. + +@c The default method accepts a string, which is expected to contain of a +@c number of integers separated by #\. characters. The method is not +@c recursive. The component satisfies the version dependency if it has +@c the same major number as required and each of its sub-versions is +@c greater than or equal to the sub-version number required. + +@c @lisp +@c (defun version-satisfies (x y) +@c (labels ((bigger (x y) +@c (cond ((not y) t) +@c ((not x) nil) +@c ((> (car x) (car y)) t) +@c ((= (car x) (car y)) +@c (bigger (cdr x) (cdr y)))))) +@c (and (= (car x) (car y)) +@c (or (not (cdr y)) (bigger (cdr x) (cdr y)))))) +@c @end lisp + +@c If that doesn't work for your system, you can override it. I hope +@c you have as much fun writing the new method as @verb{|#lisp|} did +@c reimplementing this one. +@c @end deffn + +@c @deffn Operation feature-dependent-op + +@c An instance of @code{feature-dependent-op} will ignore any components +@c which have a @code{features} attribute, unless the feature combination +@c it designates is satisfied by @code{*features*}. This operation is +@c not intended to be instantiated directly, but other operations may +@c inherit from it. + +@c @end deffn @node Creating new operations, , Predefined operations of asdf, Operations @comment node-name, next, previous, up

1 1

[asdf-devel] ASDF manual
by Robert Goldman 17 Aug '09

17 Aug '09

The asdf manual seems to document two non-existent operations: feature-dependent-op and test-system-version. Any reason not to excise them from the manual? R

2 2

[asdf-devel] and of course I forgot the attachment....
by Robert Goldman 17 Aug '09

17 Aug '09

Here's David's patch.... --- asdf.lisp-orig 2007-04-07 20:49:06.000000000 +0200 +++ asdf.lisp 2007-04-07 20:51:42.000000000 +0200 @@ -355,13 +355,22 @@ (let ((name (coerce-name system))) (block nil (dolist (dir *central-registry*) - (let* ((defaults (eval dir)) - (file (and defaults - (make-pathname - :defaults defaults :version :newest - :name name :type "asd" :case :local)))) - (if (and file (probe-file file)) - (return file))))))) + (let ((defaults (eval dir))) + (when defaults + (let* ((file (make-pathname + :defaults defaults :version :newest + :name name :type "asd" :case :local)) + #+win32 + (lnk (make-pathname + :defaults defaults :version :newest + :name name :type "asd.lnk" :case :local))) + (when (probe-file file) + (return file)) + #+win32 + (when (probe-file lnk) + (let ((target (parse-windows-shortcut lnk))) + (when target + (return (pathname target)))))))))))) (defun make-temporary-package () (flet ((try (counter) @@ -1172,6 +1181,84 @@ (hyperdocumentation (symbol-package name) name doc-type)) +;;;; Windows shortcut support. Based on: + +;;; Jesse Hager: The Windows Shortcut File Format. +;;; http://www.wotsit.org/list.asp?fc=13 + +(defparameter *link-initial-dword* 76) +(defparameter *link-guid* #(1 20 2 0 0 0 0 0 192 0 0 0 0 0 0 70)) + +(defun read-null-terminated-string (s) + (with-output-to-string (out) + (loop + for code = (read-byte s) + until (zerop code) + do (write-char (code-char code) out)))) + +(defun read-little-endian (s &optional (bytes 4)) + (let ((result 0)) + (loop + for i from 0 below bytes + do + (setf result (logior result (ash (read-byte s) (* 8 i))))) + result)) + +(defun parse-windows-shortcut (pathname) + (with-open-file (s pathname :element-type '(unsigned-byte 8)) + (handler-case + (when (and (= (read-little-endian s) *link-initial-dword*) + (let ((header (make-array (length *link-guid*)))) + (read-sequence header s) + (equalp header *link-guid*))) + (let ((flags (read-little-endian s))) + (file-position s 76) ;skip rest of header + (when (logbitp 0 flags) + ;; skip shell item id list + (let ((length (read-little-endian s 2))) + (file-position s (+ length (file-position s))))) + (cond + ((logbitp 1 flags) + (parse-file-location-info s)) + (t + (when (logbitp 2 flags) + ;; skip description string + (let ((length (read-little-endian s 2))) + (file-position s (+ length (file-position s))))) + (when (logbitp 3 flags) + ;; finally, our pathname + (let* ((length (read-little-endian s 2)) + (buffer (make-array length))) + (read-sequence buffer s) + (map 'string #'code-char buffer))))))) + (end-of-file () + nil)))) + +(defun parse-file-location-info (s) + (let ((start (file-position s)) + (total-length (read-little-endian s)) + (end-of-header (read-little-endian s)) + (fli-flags (read-little-endian s)) + (local-volume-offset (read-little-endian s)) + (local-offset (read-little-endian s)) + (network-volume-offset (read-little-endian s)) + (remaining-offset (read-little-endian s))) + (declare (ignore total-length end-of-header local-volume-offset)) + (unless (zerop fli-flags) + (cond + ((logbitp 0 fli-flags) + (file-position s (+ start local-offset))) + ((logbitp 1 fli-flags) + (file-position s (+ start + network-volume-offset + #x14)))) + (concatenate 'string + (read-null-terminated-string s) + (progn + (file-position s (+ start remaining-offset)) + (read-null-terminated-string s)))))) + + (pushnew :asdf *features*) #+sbcl

1 0

[asdf-devel] announce : 1.357
by Gary King 12 Aug '09

12 Aug '09

(small steps forward!) test-op depends on load-op (thanks to rpgoldman(a)sift.info) * Improve error message for bad dependencies * New default is for test-op to depend on load-op * tweak run-program for SBCL so that ACL isn't #+no #+no bothered * tweak write-test-web-page and write-license * tweak some tests Thanks Robert, et. al. for good discussion, etc. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

Re: [asdf-devel] About regression tests and libraries
by Tobias C. Rittweiler 12 Aug '09

12 Aug '09

Juan Jose Garcia-Ripoll writes: > What I would like to ask CL developers is to begin shipping regression > tests with their libraries, and perhaps agree on an standard so that > one can programatically check whether a library builds or not. This > feature could be even included in ASDF, asdf-install, etc, just like > "make check" is now a de-facto standad in Autoconf. There's (ASDF:OOS 'ASDF:TEST-OP <system>), and on very recent revisions even (ASDF:TEST-SYSTEM <system>) as an abbeviation. I don't think this has been properly documented in the manual of ASDF yet. I hence CC'd the asdf-devel mailing list so this will hopefully get promoted with the due it deserves. -T.

7 20

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel August 2009