- asdf-devel - mailman3.common-lisp.net

[asdf-devel] Minor simplification
by Juan Jose Garcia-Ripoll 06 Feb '11

06 Feb '11

Right now there are hooks in ASDF which are used by ECL in a perhaps too complicated way. More precisely, ECL requires to make an object file and a FASL file out of every compiled file, so that other operations (LOAD-FASL-OP, monolithic building, standalone executables, etc) become easier. Right now this is done using an :AFTER method on PERFORM. I suggest this patch (already in ECL's tree) which removes that method, removes the upgradability hacks and insteads wraps around COMPILE-FILE* (which now becomes redefinable at run time). Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

3 14

[asdf-devel] Issues with logical pathnames in Allegro and clisp
by Pascal Costanza 25 Jan '11

25 Jan '11

Hi, I have encountered two more issues when trying to use ASDF 2 with logical pathnames in Allegro and clisp. I have the following logical pathname translations in Allegro and clisp respectively: #+allegro (setf (logical-pathname-translations "costanza") `(("**;*.fasl.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fasl" (lisp-implementation-type) (read-from-string (lisp-implementation-version)))) ("**;*.*.*" "/Users/costanza/**/*.*"))) #+clisp (progn (setq custom:*parse-namestring-ansi* t) (setf (logical-pathname-translations "costanza") `(("**;*.lib.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.lib" (lisp-implementation-type) (read-from-string (lisp-implementation-version)))) ("**;*.fas.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fas" (lisp-implementation-type) (read-from-string (lisp-implementation-version)))) ("**;*.*.*" "/Users/costanza/**/*.*")))) When compiling systems with ASDF, however, the fasl, lib and fas files don't end up in the folders designated by these logical pathname translations, but rather in the locations as specified with ASDF output translations. (In CMUCL, Clozure, ECL, LispWorks, RMCL, and SBCL, similar logical pathname translations work as expected.) I have not defined any ASDF output translations of my own, but I'm using quicklisp, which probably does this. Please let me know if I can do something to help fixing this problem. Thanks, Pascal -- Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net Vrije Universiteit Brussel Software Languages Lab Pleinlaan 2, B-1050 Brussel, Belgium

3 6

[asdf-devel] ASDF with RMCL?
by Pascal Costanza 23 Jan '11

23 Jan '11

Hi, It seems that ASDF 2.x doesn't work with RMCL (ASDF 1.x did). Is that a known issue? Best, Pascal -- Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net Vrije Universiteit Brussel Software Languages Lab Pleinlaan 2, B-1050 Brussel, Belgium

4 16

[asdf-devel] ASDF 2.012
by Faré 03 Jan '11

03 Jan '11

I finally released ASDF 2.012, which is 2.011.9 being blessed. Since the previous release 2.011, there have been several minor improvements. Nothing serious or urgent, as ASDF 2 is getting mature, but it would be great if implementations were to update their version of ASDF to this latest release. Changes: Added :here directive to pathname DSL, robustified ECL support, fixed infinite loop when filesystem clock is in the future, extended the AOT DSL and made it more futureproof, fixed how clear-system interacts with map-systems, fixed use of directory under old SBCLs, fixed run-shell-command status and version string under clisp, fixed error messages. In the master (development) branch, I committed further cleanups as 2.012.1. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] For pretty much every writer, the big problem isn't piracy, it's obscurity. — Tim O'Reilly, as cited by Cory Doctorow

1 0

[asdf-devel] creating a distribution using asdf
by Sam Steingold 31 Dec '10

31 Dec '10

Hi, How do I distribute an application built using asdf? Specifically, given file foo.lisp, I need the list of all the fasl files of all the files on which foo.lisp depends (+ foo.fasl) in the correct order of loading. Thanks! -- Sam Steingold (http://sds.podval.org/) on Ubuntu 10.04 (lucid) http://iris.org.il http://ffii.org http://memri.org http://jihadwatch.org http://palestinefacts.org http://openvotingconsortium.org I'd give my right arm to be ambidextrous.

2 3

[asdf-devel] asdf 2.012 to be released on dec 31.
by Faré 28 Dec '10

28 Dec '10

I intend to release asdf 2.012 on dec 31. Hopefully, it would be my last release, and I would push for it to be included in all implementations. It would be nice if you would test the latest asdf 2.011.x to work on your platform before I do, maybe even try our regression test suite. Windows testers are particularly sought, since none of the maintainers seem to use windows. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Always design a thing by considering it in its next larger context — a chair in a room, a room in a house, a house in an environment, an environment in a city plan. — Eliel Saarinen

3 3

[asdf-devel] New test and windows
by Robert Goldman 28 Dec '10

28 Dec '10

I pushed a new test for asdf:run-shell-command that I believe will not work on Windows. The first step should be to use reader switches to remove the test contents when running on Windows, but ideally we should supply some windows code to take the place of the posix code where appropriate. The current test relies on /usr/bin/true and /usr/bin/false to test how asdf:run-shell-command checks exit codes. To be honest, I don't even know if Windows commands /have/ exit codes! See tests/run-shell-command-test.script I suspect that this means no one is running these tests, since there hasn't been a loud cry of outrage!

3 8

[asdf-devel] Replace *DEFAULT-PATHNAME-DEFAULTS*
by Thomas M. Hermann 24 Dec '10

24 Dec '10

There are several places where ASDF relies on *DEFAULT-PATHNAME-DEFAULTS* to provide a default path. The value of this variable is "An implementation-dependent pathname, typically in the working directory that was current when Common Lisp was started up." [ http://www.lispworks.com/documentation/HyperSpec/Body/v_defaul.htm ] I think it would be better to define a variable, like asdf:*pathname-defaults*, asdf:*registry-pathname-defaults, etc., that is explicitly set using feature expressions. The biggest argument for not making this change is that some systems may rely on the value of *DEFAULT-PATHNAME-DEFAULTS*. I don't think it would be too difficult to correct those systems, but admit that it might not be worth the effort. My motivation for making this change was prompted by the function default-source-registry. It creates a :directory entry in the source registry that is constructed from the TRUENAME of the value returned by *DEFAULT-PATHNAME-DEFAULTS*. The first point is that the value *DEFAULT-PATHNAME-DEFAULTS* is implementation dependent. For the cases I tested using CCL 1.6 and LispWorks 6.0.1 on Windows 7, the value is the empty path #P"". The second point is that the pathname returned by TRUENAME when it is given the empty path is implementation dependent. In the case of CCL, (TRUENAME #P"") returns the working directory that was current when Common Lisp was executed. In the case of LispWorks, (TRUENAME #P"") returns #P"C:/Windows/system32/". This may be the working directory that was current when LispWorks was started, but it is clearly not a desirable place for ASDF systems. In either case, the result is a :directory entry in the source registry that is not well defined. I think it is better to have the default pathname well defined. Thank you, ~ Tom ---------------------------------------------------------------- Thomas M. Hermann Odonata Research LLC http://www.odonata-research.com/ http://www.linkedin.com/in/thomasmhermann

3 5

[asdf-devel] textual representation of plan, asdf:explain
by Tobias C Rittweiler 15 Dec '10

15 Dec '10

What is the way to get a textual representation of the plan of a system? I would have thought that this is what ASDF:EXPLAIN is for, but grepping through asdf.lisp did not make me believe that's true. Also, is there some fundamental reason why (asdf:explain 'asdf:compile-op :system-name) could not be the interface for ASDF:EXPLAIN? -T.

2 1

[asdf-devel] ASDF Git: please remove tags, etc.
by Faré 15 Dec '10

15 Dec '10

Apparently, for quite a few months (did it start with me or with gwking?), we've been misusing git tag -f FOO as if the latest version of the tag would be propagated when we push, whereas it isn't - on purpose - since tags are meant to be constant. I invite all committers to run the following Makefile target to erase git tags that have been misused this way, as well as an obvious typo: make fix-local-git-tags (That would be mostly me and rpg). It's not a bad thing to do if you're using ASDF from git, even without being a committer. To future maintainers: I have also written a script bin/bump-version.sh to bump the version. For users, since 2.011, we've improved the source-registry and output-translations configuration DSLs, given examples in the documentation of how to configure AOT to store things in a subdirectory of the current one, and made, fix a bug in corner cases, etc. I intend to release 2.012 before the end of the year. Will hopefully be my last. (I've said that in the past.) I took over the asdf-announce mailing-list for announcing releases. I invite Lisp implementers, distribution makers, etc., to subscribe to it (rather than to this mailing-list) to know when to update their software. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] No man would listen to you talk if he didn't know it was his turn next. — Edgar Watson Howe

1 0