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

[asdf-devel] patch system-source-file
by Greg Pfeil 25 Sep '09

25 Sep '09

Here are a couple changes to ASDF that I made in the process of creating an ASDF browser for CCL's IDE: • system-source-file now works for systems without their own .asd • optional parts of systems (version, maintainer, etc.) don't leave their slots unbound

7 17

[asdf-devel] directly evaluating .asd file
by Tobias C. Rittweiler 25 Sep '09

25 Sep '09

Visiting an .asd file and using C-c C-k to compile-and-load would make the system properly available in past. This does not seem to work since a few revisions. It now tries to load the files specified in the system relative to the current working directory. When I C-c C-l, that is just load without compiling, it still works as it did in past. Is this a known regression? -T.

1 0

[asdf-devel] [RfC] default value for *central-registry*
by Tobias C. Rittweiler 24 Sep '09

24 Sep '09

I hate that I have to push a commonly shared directory onto *central-registry* for each implementation and thus have to know the rc files of every implementation. (I was recently bidden by some classic rm -rf ~, and had to redo all these kinds of infrastructure woes.) Would anyone mind ASDF coming with an additional default value of ~/.asdf/systems/? -T.

6 10

[asdf-devel] updating ccl's bundled asdf
by R. Matthew Emerson 24 Sep '09

24 Sep '09

[sorry if this is duplicate] We bundle an ASDF version that's about a year old or so (1.130) with Clozure CL. If I want to bundle a newer ASDF with CCL, what version should it be? There seem to have been half a dozen releases in the past couple of months. Would it be best to wait a little longer for things to settle down?

4 6

[asdf-devel] ASDF features under discussion
by Juan Jose Garcia-Ripoll 23 Sep '09

23 Sep '09

Now that this discussion is opened, I would like to add a small question and a petition. First the question. What is the level of integration of ASDF with different implementations? Does ASDF support all lisp implementations equally? Does SBCL (and perhaps other) ship the latest versions of ASDF? I am asking this because ECL has some pretty special needs. Namely, ASDF currently relies on compile-file / load for everything and for us it is more efficient to compile many files into a single binary that is loaded at a later point. Currently ECL solves this using a slightly outdated version of ASDF, providing its own operations and imposing around methods on different operations. http://ecls.git.sourceforge.net/git/gitweb.cgi?p=ecls/ecl;a=blob;f=contrib/… For instance, we have a LOAD-FASL-OP that joins three steps: 1) a LOAD-OP that thanks to the around methods produces both FASLs and object files, 2) linking the object files into a big FASL, 3) loading the big FASL. If the big FASL has been produced, then only step 3) is performed. But in addition to this ECL provides operations for creating standalone executable files, shared libraries and statically linked libraries http://ecls.sourceforge.net/new-manual/ch16.html I am aware that ASDF is a rapidly evolving architecture and I am afraid that things would break. It is for this reason that I would like to ask for help in one of these ways: 1) providing a stable way for us to implement these extensions or 2) including those operations in ASDF. Juanjo On Wed, Aug 19, 2009 at 3:11 PM, Gary King<gwking(a)metabang.com> wrote: > 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. -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

5 7

[asdf-devel] ccl's bundled asdf
by R. Matthew Emerson 22 Sep '09

22 Sep '09

Clozure CL bundles an ASDF version that's about a year old or so (1.130). If I want to bundle a newer ASDF with CCL, what version should it be? There seems to have been half a dozen releases in the past couple of months. Maybe I should wait a little longer for things to settle down?

1 0

[asdf-devel] (no subject)
by Nick Levine 16 Sep '09

16 Sep '09

Hi. Can anyone point me to a list of which lisps do / don't run ASDF? Or is it believed that all CL implementations work with ASDF? Thanks, - nick

4 3

[asdf-devel] link to asdf git repo
by Gary King 13 Sep '09

13 Sep '09

Hi Angel, I just tried git clone http://common-lisp.net/project/asdf/asdf.git and it worked. Can you please send the error message you saw? thanks, -- 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] link to asdf git repo
by Angel Popov 13 Sep '09

13 Sep '09

Hi, It looks that link to git repo of asdf does not work. on page http://common-lisp.net/project/asdf/ doing git clone http://common-lisp.net/project/asdf/asdf.git gives error. Regards, AngelP

1 0

[asdf-devel] Recognizing directories in a component name
by Faré 13 Sep '09

13 Sep '09

For years now, we at ITA have been satisfied with a patch that does the following while building QRes: allow to specify module names that include a directory component, without having to redundantly as in (:module "subdir1/subdir2" :components ((:file "subdir3/name3") (:file "subdir4/name4.subname4"))) instead of the cumbersome (to be portable): (:module "subdir1/subdir2" :pathname #.(make-pathname :directory '(:relative "subdir" "subdir2")) :components ((:file "subdir3/name3" :pathname #.(make-pathname :directory '(:relative "subdir3" :name "name3"))) (:file "subdir4/name4.subname4" :pathname #.(make-pathname :directory '(:relative "subdir4" :name "name4.subname4")))))) Since there is active ASDF development again, I cleaned it up and here it is. The methods should replace those currently in ASDF. The helper function now uses the existing ASDF split function (as previously requested by Xof). The patch is both backwards compatible and portable, in that * the "/" character was previously forbidden in names of portable components without a :pathname statement, least it breaks miserably on most platforms. * the "/" character is now recognized by ASDF itself as a separator for directories later made with make-pathname, thus doing what is expected even on the odd platform without "/" as the pathname separator. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Selfishness is the measure of all good (and bad) in the world. There cannot be any good whatsoever without a self to feel it. WHO is whatever "altruistic" oppression ever good for? No one. Why is gratuitous vandalism or well-intentioned mass murder bad? Not because it is selfish, but precisely because it hurts other people's selfish interest.

3 5