asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[asdf-devel] (asdf:load-system :iterate) loads :iterate-pg & :iterate-tests
by Frank 02 Apr '11

02 Apr '11

Hello there, I've been using iterate for a short while. I noticed that it always loads :iterate-pg and :iterate-tests on (asdf:load-system :iterate). Do those modules have to be pulled in for just the basic :iterate part? I'm using ccl-1.6 and the quicklisp iterate version. Thanks Frank

2 1

[asdf-devel] ASDF 2.014 released
by Faré 31 Mar '11

31 Mar '11

Dear ASDF users, I just blessed ASDF 2.013.7 as 2.014. As compared to 2.013, it includes a significant quality item that makes it essential for everyone who distributes ASDF without an implementation (e.g. Quicklisp). It also includes better SCL support, cosmetic improvements, and robustification of some corner cases. Tests have been added to prevent the regressions observed in the 2.013 release. * Fixed bug preventing upgrade from 2.000 to 2.008 (test added) * Better support for URL pathnames on SCL (test added) * Robustified defsystem-depends-on * Cosmetic changes: * better more portably readable error messages. * remove forward references, again (test added) * canonicalize system names earlier (slight robustness improvement) As usual, I invite people who distribute ASDF to update the version they ship, be it with their implementations, with their software distribution, etc. Happy Happy Joy Joy [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] "Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats." — Howard Aiken

2 7

[asdf-devel] ASDF and XCL
by Azamat S. Kalimoulline 31 Mar '11

31 Mar '11

XCL has realization of getenv CL-USER(1): (getenv "HOME") "/home/turtle" But ASDF says that no. -- WBR Turtle//BAZON Group

2 1

[asdf-devel] CONSTANTLY in HANDLER-BIND
by Sam Steingold 29 Mar '11

29 Mar '11

Hi, MODULE-PROVIDE-ASDF used CONSTANTLY in HANDLER-BIND to define a handler. IIUC, this merely delegates error handling further, so it is more or less dead code. Is this intentional? -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.5 (Final) X http://pmw.org.il http://iris.org.il http://www.PetitionOnline.com/tap12009/ http://palestinefacts.org http://jihadwatch.org http://honestreporting.com If you want it done right, you have to do it yourself

2 1

[asdf-devel] Small patch for cmucl and subdirectories
by Raymond Toy 28 Mar '11

28 Mar '11

Currently, cmucl fails the asdf test test-configuration. This is because SUBDIRECTORIES returns the wrong things. The test prints out the following before failing because foo1.asd cannot be found: subdirectories of dir2/: (#P"/Volumes/share2/src/clnet/asdf/tmp/dir2/dir3/foo1.asd" #P"/Volumes/share2/src/clnet/asdf/tmp/dir2/dir4/foo2.asd") subdirectories of dir5/: (#P"/Volumes/share2/src/clnet/asdf/tmp/dir5/dir6/foo4.asd" #P"/Volumes/share2/src/clnet/asdf/tmp/dir5/dir7/foo5.asd") 0: (PROCESS-SOURCE-REGISTRY WRAPPING-SOURCE-REGISTRY :REGISTER #<Closure Over Function "DEFUN* FLATTEN-SOURCE-REGISTRY" {48342C89}> :INHERIT ...) 0: PROCESS-SOURCE-REGISTRY returned NIL Source Registry: ((#P"/Volumes/share2/src/clnet/asdf/tmp/dir1/" #P"/Volumes/share2/src/clnet/asdf/tmp/dir2/" #P"/Volumes/share2/src/clnet/asdf/tmp/dir2/dir3/foo1.asd" #P"/Volumes/share2/src/clnet/asdf/tmp/dir2/dir4/foo2.asd" #P"/Volumes/share2/src/clnet/asdf/tmp/dir5/dir6/" #P"/Volumes/share2/src/clnet/asdf/tmp/dir8/" #P"/Volumes/share2/src/clnet/asdf/tmp/dir9/dira/" #P"/Volumes/share2/src/clnet/asdf/tmp/dir9/dira/dirc/foo8.asd")) ;; Loading #P"/Volumes/share2/src/clnet/asdf/tmp/dir1/foo0.asd". Here is a small patch for SUBDIRECTORIES that makes it return the expected subdirectories. This basically makes cmucl use the same code path as scl. If this doesn't make it into another asdf release before the cmucl snapshot due in a week or so, I'll apply this patch to cmucl's version for now. Ray diff --git a/asdf.lisp b/asdf.lisp index 1d3e0b5..4d078ae 100755 --- a/asdf.lisp +++ b/asdf.lisp @@ -3521,9 +3521,9 @@ with a different configuration, so the configuration would be re-read then." (let* ((directory (ensure-directory-pathname directory)) #-(or cormanlisp genera) (wild (merge-pathnames* - #-(or abcl allegro lispworks scl) + #-(or abcl allegro lispworks scl cmu) *wild-directory* - #+(or abcl allegro lispworks scl) "*.*" + #+(or abcl allegro lispworks scl cmu) "*.*" directory)) (dirs #-(or cormanlisp genera) @@ -3532,7 +3532,7 @@ with a different configuration, so the configuration would be re-read then." #+mcl '(:directories t)))) #+cormanlisp (cl::directory-subdirs directory) #+genera (fs:directory-list directory)) - #+(or abcl allegro genera lispworks scl) + #+(or abcl allegro genera lispworks scl cmu) (dirs (remove-if-not #+abcl #'extensions:probe-directory #+allegro #'excl:probe-directory #+lispworks #'lw:file-directory-p

1 0

[asdf-devel] Patch: Rework output formats.
by Douglas Crosher 26 Mar '11

26 Mar '11

Attached is a patch that reworks the output formats to better fit the stream width. A new macro 'compatfmt is added that strips out commands that are not supported by Genera. Regards Douglas Crosher

2 1

[asdf-devel] asdf 2.014 soon?
by Faré 25 Mar '11

25 Mar '11

OK, considering the many small things I didn't get right in 2.013, I intend to release a 2.014 by the end of next week. Now would be a good time to test the latest ASDF (currently 2.013.6), or write tests for your favorite functionality, report a bug, etc. I've added tests for the most glaring annoyances of 2.013 (a trivial upgrade test, and a test of no forward-reference warning when loading under SBCL). [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The highest goal of computer science is to automate that which can be automated. — Derek L. VerLee

1 0

[asdf-devel] FWIW
by Robert Goldman 25 Mar '11

25 Mar '11

I just pulled the update and ran tests on Mac OSX: CCL 64-bit Allegro Allegro modern ABCL SBCL all passed. ABCL and CCL are a little bit short of bleeding edge, FWIW.

1 0

[asdf-devel] Messages are a bit uglier now
by Zach Beane 24 Mar '11

24 Mar '11

Sorry for not following the line wrapping discussion earlier. Now that I've had a chance to build some systems, the new output looks a bit ugly to me. Here's how 2.010 looked: * (asdf:load-system "my-very-long-system-woo-hoo") ; loading system definition from ; /home/xach/src/asdf/my-very-long-system-woo-hoo.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM #:MY-VERY-LONG-SYSTEM-WOO-HOO> as ; MY-VERY-LONG-SYSTEM-WOO-HOO T Here's how 2.013.4 looks: * (asdf:load-system "my-very-long-system-woo-hoo") ; Loading system definition from /home/xach/src/asdf/my-very-long-system-woo-hoo.asd into #<PACKAGE "ASDF0"> ; Registering #<SYSTEM #:MY-VERY-LONG-SYSTEM-WOO-HOO> as MY-VERY-LONG-SYSTEM-WOO-HOO T I thought it might be improved by setting *print-pretty* to nil, but that still produces this: * (asdf:load-system "my-very-long-system-woo-hoo") ; Loading system definition from /home/xach/src/asdf/my-very-long-system-woo-hoo.asd into #<PACKAGE "ASDF0"> ; Registering #<SYSTEM #:MY-VERY-LONG-SYSTEM-WOO-HOO> as MY-VERY-LONG-SYSTEM-WOO-HOO T It looks like there are extra blank lines before each message. In case your mail client makes the wrapping look weird, I also pasted these examples at http://paste.lisp.org/display/120843/raw. I really prefer the older output. If the newer output is kept, it would be nice if the extra blank lines could be eliminated. Thanks, Zach

3 4

[asdf-devel] Didn't you fix this bug?
by Robert Goldman 23 Mar '11

23 Mar '11

I believe you have already not just committed, but released, a fix, and we also have a test now. https://bugs.launchpad.net/asdf/+bug/732317 Want to clear this (credit where credit is due)? If you don't have time, drop me a line, and I can. cheers, r

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel