asdf-devel September 2009

asdf-devel@common-lisp.net

18 participants
27 discussions

[asdf-devel] Two questions
by Nick Levine 17 Nov '09

17 Nov '09

1. Problems with the :feature feature. (asdf:defsystem foo :components ((:file "pkg") (:file "code") (:file "foo" :depends-on ((:feature :frob))))) If :frob is not on *features*, load-system gives me: Error: Bad dependency (FEATURE FROB). Dependencies must be (:version <version>), (:feature <feature>), or a name If :frob is a *feature* I get a different error: Error: Error component :FROB not found, required by #<CL-SOURCE-FILE "foo" #x8B7A3E6> Did I misunderstand something? 2. Suppose I would like some code to run at compile-time / load-time to determine where the fasls should live (e.g. hypothetically, in a subdirectory named after a timestamp, or according to what patches I have loaded). How do I express this? (I'm using version 1.363) Thanks. - nick

8 16

[asdf-devel] recursiveness of :FORCE
by Tobias C. Rittweiler 09 Nov '09

09 Nov '09

When I use :FORCE, in most cases I do want to recompile solely the specified system, not all its dependencies. In my ideal world, :FORCE T would recompile the specified system only, and :FORCE :ALL would recompile it along its dependencies. Of course that would be backwards-incompatible, so perhaps better stick with the current behaviour for :FORCE T, but add :FORCE :SYSTEM, or :FORCE :SHALLOW, or similiar. -T.

2 5

[asdf-devel] summary proposal for COMMON_LISP_PATH and system search changes
by Gary King 08 Oct '09

08 Oct '09

Here is a summary of what I've heard and what I think we should do. # Proposal Summary These are independent but make the most sense if taken as a whole. * Specify new defaults for `*central-registry*`, * use an environment variable named `COMMON_LISP_PATH` to override ASDF's defaults, * use `*central-registry*` to find and load an ASDF configuration file (if present) and * modify the default behavior of `sysdef-central-registry-search` to search deeply. ## default value for *central-registry* COMMON_LISP_PATH environment variable with syntax like path[;path]* This is used by ASDF to help build the default value for `*central-registry*`. If not specified, `*central-registry*` defaults to (on *nix-like systems): (list *default-pathname-defaults* (merge-pathnames (make-pathname :directory '(:relative ".common-lisp")) (user-homedir-pathname))) (merge-pathnames (make-pathname :directory '(:relative ".local" "share" "common-lisp")) (user-homedir-pathname))) (make-pathname :directory '(:absolute "usr" "local" "share" "common-lisp")) (make-pathname :directory '(:absolute "usr" "share" "common- lisp")) ) (The last two would need to be different for Windows-based systems.) ## modification for `sysdef-central-registry-search` Currently `sysdef-central-registry-search` searches in the top-level of each directory in `*central-registry*` to find systems. If we use the above, then a more useful approach would be to search in the top-level and in a sub-directory named `systems`. An even more useful approach would to search in all sub-directories of each entry. ## configuration file When ASDF starts, it will: 1. setup `*central-registry*` using its own defaults and the `COMMON_LISP_PATH` environment variable. 2. look for (and load if it is found) a file named `asdf-config.lisp` in each of these paths traversed in _reverse_ order (so that user settings take precedence overs system ones). Note that the ASDF package will exist when this file is read. I.e., I'm suggesting that we go the "user settings overwrite system settings" route rather than the "if there are any user settings, then ignore the system settings" one. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

8 20

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

28 Sep '09

2009/9/27 Gary King <garywarrenking(a)gmail.com>: > This is _finally_ out; please let me know if anything seems amiss. Thanks a lot! What you have does the trick for me wrt directories in the name, but now that I think of it, to fully solve the problem of source-file-type being NIL (for e.g. static-file) as experienced by several other hackers (and me before I tweaked my .asd files), a cleaner and more effective version should be as attached. I also updated the test script to actually work, as opposed to dying after the first quit-on-error (that also quits without error). I also renamed the fasl directory to .cache/common-lisp/ which you might want to undo. I added newlines in the script-support results. I moved around a function to remove an annoying "undefined function" (actually forward reference) message when loading asdf on SBCL. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Time and money spent in helping men to do more for themselves is far better than mere giving. -- Henry Ford

1 0

[asdf-devel] announce: asdf 1.366
by Gary King 27 Sep '09

27 Sep '09

Thanks to all the contributions and please let me know if anything seems awry. * rename *place-binaries-in-implementation-specific-directories* to *enable-asdf-binary-locations* * Daniel Herring's CLISP/Windows/Symlink patch #+(and (or win32 windows) (not :clisp)) * Faré's patch for better module-pathname handling * test for same * Fix for my head-slap regex s&r madness. -- 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] Obscure A-B-L bug?
by Daniel Herring 26 Sep '09

26 Sep '09

Hi, The following is representative of an obscure bug I'm trying to resolve (without direct access to the computer). It affects A-B-L 0.3.8 and a recent release of ASDF, but I don't see any relevant changes to either project in the past couple years. To set up this example, # cd /path/to/.asdf # ln -s ../asdf-binary-locations/asdf-binary-locations.asd . Then under LispWorks on a PPC mac, CL-USER > (push #P"/path/to/.asdf/" asdf:*central-registry*) CL-USER > (asdf:operate 'asdf:load-op :asdf-binary-locations) ; loading system definition from ; /path/to/.asdf/asdf-binary-locations.asd into ; #<The ASDF0 package, 0/16 internal, 0/16 external> ; Loading text file /path/to/.asdf/asdf-binary-locations.asd ; registering #<SYSTEM ASDF-BINARY-LOCATIONS 200B9373> as ASDF-BINARY-LOCATIONS Error: The file #P"/path/to/.asdf/dev/main.lisp" does not exist. ASDF is clearly resolving the symlink to read A-B-L.asd; but its using the wrong path to load the source files. Is the custom load-op for load-only-cl-source-file somehow skipping the normal truename/path merging process? Any other ideas or things to look for? Thanks, Daniel

3 2

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel September 2009