- 06 Feb, 2011 1 commit
-
-
Francois-Rene Rideau authored
-
- 05 Feb, 2011 1 commit
-
-
Francois-Rene Rideau authored
-
- 24 Jan, 2011 1 commit
-
-
Francois-Rene Rideau authored
-
- 20 Jan, 2011 1 commit
-
-
Francois-Rene Rideau authored
-
- 03 Jan, 2011 3 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- 23 Dec, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 21 Dec, 2010 1 commit
-
-
Francois-Rene Rideau authored
Thanks to Stas Boukarev.
-
- 16 Dec, 2010 1 commit
-
-
Francois-Rene Rideau authored
whose DIRECTORY doesn't have RESOLVE-SYMLINKS.
-
- 15 Dec, 2010 1 commit
-
-
Francois-Rene Rideau authored
Fixes lp#690814 (thanks, Xach).
-
- 10 Dec, 2010 2 commits
-
-
Francois-Rene Rideau authored
Updating both asdf.asd and asdf.lisp is manual for now. Script help needed.
-
Francois-Rene Rideau authored
add condition class(es) for configuration processing failures (lp#684332), don't try (and fail) getting the architecture under CLISP (lp#688228).
-
- 04 Dec, 2010 1 commit
-
-
Francois-Rene Rideau authored
The issue was reported by Sid H <shortsightedsid@gmail.com> on asdf-devel. Problem is, when the filesystem server clock is in the future of the system clock (either because the NFS server has a clock in the future, or because the lisp host has a clock in the past), defsystem would call find-system (via find-component via parse-component-form) to make sure it modifies any previously registered object if any, rather than create a new object with "interesting" consequences if anyone held to the previous object. find-system would see the file has been modified since last registered with register-system, and proceed to load again, in an infinite loop that stop either when the Lisp process runs out of stack, or the date and time specified in the timestamp is reached. Now, ASDF doesn't bother reloading if the timestamp is in the future.
-
- 03 Dec, 2010 1 commit
-
-
Francois-Rene Rideau authored
Apparently, :unspecific as pathname type isn't that well liked by ECL.
-
- 02 Dec, 2010 2 commits
-
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
- 29 Nov, 2010 7 commits
-
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
- 28 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 23 Nov, 2010 2 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- 22 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 19 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 15 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 14 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 05 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 04 Nov, 2010 1 commit
-
-
Francois-Rene Rideau authored
Makes cl-launch -B print_lisp_setup happier by not having uncommented upgrade words in the standard output stream. Reorder some sections of text, so we can use asdf-message during u-i-f-r-c.
-
- 29 Oct, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 28 Oct, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 27 Oct, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 26 Oct, 2010 1 commit
-
-
Francois-Rene Rideau authored
-
- 25 Oct, 2010 2 commits
-
-
Francois-Rene Rideau authored
Actually, there's no way to automatically make sure that the ASDF version number is consistent between the asdf.asd and the asdf.lisp, lest we have scripts that enforce it at checkin or checkout time.
-
Francois-Rene Rideau authored
in vain attempt to shorten pathnames on Windows. See lp#665657 and the 260 char limit of Windows pathnames(!)
-
- 23 Oct, 2010 1 commit
-
-
Francois-Rene Rideau authored
-