asdf-devel September 2010

asdf-devel@common-lisp.net

13 participants
15 discussions

[asdf-devel] Directly loading "/home/etc/etc/system.asd"
by Theam Yong Chew 09 Nov '10

09 Nov '10

Hi all, Is there a way to load a system directly, leaving everything else (source-registry configuration, *central-registry*, or what not) alone? I hacked up something to do this, (asdf:load-system #P"c:/blah/blah/cl-ppcre-1.2.19/cl-ppcre.asd") so that there's no need to worry about specific versions or setting up paths to a specific library. If the library being loaded depends on other modules, then we return to searching the source-registry as if by typing this before loading our system: (asdf:load-system <lib-depended-upon>) Does asdf already support this? Will such a feature be useful? Yong.

2 1

[asdf-devel] ASDF 2 questions
by Didier Verna 10 Oct '10

10 Oct '10

[ Please, Cc: me as I'm not on the mailing list ] Hi, I'm trying to upgrade my CL configuration to ASDF 2, and I have several questions: 1/ why isn't "source-registry.conf" named "asdf-source-registry.conf" ? 2/ Should we understand that the convention of having a "systems" directory with .asd files symlinked there is now obsolete ? I still prefer to keep that because I can select which of the installed sources I do want to be seen. I guess you could also use exclude patterns for doing so, but it seems way more complicated. Comments ? 3/ The following contents for source-registry.conf fails: (:source-registry (:directory (merge-pathnames "share/common-lisp/systems/" (user-homedir-pathname))) (:directory "/usr/local/share/common-lisp/systems") (:directory "/usr/share/common-lisp/systems") :inherit-configuration) Am I to understand that this file cannot really contain Lisp code (and so I couldn't use #'merge-pathnames)? Because in that case, this sucks. I have several machines on which $HOME is different (e.g. /home/ or /Users/, and no, I don't want to create a /home/ -> /Users/ symlink on my Macs) 4/ I'm also struggling with the output translations. I'm happy with the default settings (using .cache/blabla) except for one case. For lisp files located under ~/Science/Source/Common Lisp/ (recursively), I want the compiled files to remain at the same place, under an implementation-specific subdirectory, like asdf-binary-locations did for me before. For instance, ~/Science/Source/Common Lisp/foo/bar/baz.lisp would produce somthing like: ~/Science/Source/Common Lisp/foo/bar/sbcl-1.0.32.30-linux-x86-64/baz.fasl I tried this: (:output-translations ("/Users/didier/Science/Source/Common Lisp/" (:current-directory :implementation)) :inherit-configuration) but this doesn't work. SBCL says: This is SBCL 1.0.42.52, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ; loading system definition from ; /usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd into #<PACKAGE "ASDF0"> ASDF could not load sb-grovel because :CURRENT-DIRECTORY fell through ETYPECASE expression. Wanted one of ((EQL :DEFAULT-DIRECTORY) (EQL :SYSTEM-CACHE) (EQL :USER-CACHE) (EQL :HOME) (EQL :ROOT) CONS STRING PATHNAME).. ASDF could not load asdf-install because Error while trying to load definition for system sb-bsd-sockets from pathname /usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd: :CURRENT-DIRECTORY fell through ETYPECASE expression. Wanted one of ((EQL :DEFAULT-DIRECTORY) (EQL :SYSTEM-CACHE) (EQL :USER-CACHE) (EQL :HOME) (EQL :ROOT) CONS STRING PATHNAME).. debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR: Error while trying to load definition for system sb-bsd-sockets from pathname /usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd: :CURRENT-DIRECTORY fell through ETYPECASE expression. Wanted one of ((EQL :DEFAULT-DIRECTORY) (EQL :SYSTEM-CACHE) (EQL :USER-CACHE) (EQL :HOME) (EQL :ROOT) CONS STRING PATHNAME). So what's the magick ? 5/ Finally, I would like confirmation that ASDF now handles outdated fasl's correctly, and we don't need to do the black magick ourselves. Thanks a lot ! -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com

3 7

[asdf-devel] defsystem behaviour
by Daniel Barlow 01 Oct '10

01 Oct '10

Apologies for the complete lack of references headers in this mail, but I'm not subscribed to asdf-devel and only see this message in the common-lisp.net archive. On 9/13/10 Sep 13 -8:05 AM, Serhiy Yakovyn wrote: > Is this done intentionally? Robert Goldman rpgoldman at sift.info wrote: > Yes, this is done intentionally. Canonical (i.e., what you get when you > translate a symbol) names for ASDF systems (and other ASDF components) > are downcased. > I /suspect/ (I am not privy to the intentions of the original developer) > that this is because the downcased names --- this policy is applied not > just to systems, but to other components as well --- map better to the way people use modern file-systems. This is, or was once, or should be, a matter of record. I don't know where asdf is currently hosted nor how far back the revision history there goes, but if you look at a sufficiently ancient version of asdf/README you should find something like 122 *** Component Attributes 123 124 **** A name (required) 125 126 This is a string or a symbol. If a symbol, its name is taken and 127 lowercased. The name must be a suitable value for the :name initarg 128 to make-pathname in whatever filesystem the system is to be found. 129 130 The lower-casing-symbols behaviour is unconventional, but was selected 131 after some consideration. Observations suggest that the type of 132 systems we want to support either have lowercase as customary case 133 (unix, mac, windows) or silently convert lowercase to uppercase 134 (lpns), so this makes more sense than attempting to use :case :common, 135 which is reported not to work on some implementations -dan

2 1

[asdf-devel] Some points raised
by Juan Jose Garcia-Ripoll 26 Sep '10

26 Sep '10

http://groups.google.com/group/comp.lang.lisp/msg/93a4b06a66b0b335 1- The new configuration and file searching mechanism is causing some grief. 2- Lack *-user mailing list and need of subscription for questions. Is there a sufficiently large comunity here and do we want to open the list? I would ignore the other complains of a user that woke up with a bad temper. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

3 10

[asdf-devel] What is broken with asdf-devel ...
by edgar 26 Sep '10

26 Sep '10

Robert Goldman wrote: What is broken about having people post questions to asdf-devel? Just simple: unexceptionally *all* of my posts to asdf-devel so far got bounced back because my posts allegedly reach a spam level of 100%, so there is no way at all for me to ask for help. [Note that this is only another spam filter test, if this message gets bounced back again I will reply to the private email adresses] - edgar -- The author of this email does not necessarily endorse the following advertisements, which are the sole responsibility of the advertiser:

2 2

[asdf-devel] New ASDF maintainer sought
by Faré 23 Sep '10

23 Sep '10

Dear all, I hope that 2.008 will be my last ASDF release. I may still make emergency bug fixes (if any is needed), or merge patches sent to me, but I don't intend to actively develop ASDF anymore. I feel it has reached the point where I wanted it to be, although it took much more efforts than I feared. Just look at the git log to see how hard it was, and read my and Robert's paper for ILC'2010 to get an idea why we did things that way. http://common-lisp.net/project/asdf/ilc2010draft.pdf And so, ASDF is looking for a new active maintainer. To volunteer, just start hacking on your own repo, and I'll hand you the keys after I merge your first commit. I intend to focus on XCVB, and its dependencies, cl-iolib and libfixposix. If ASDF moves towards more declarative .asd files, XCVB will certainly try to be compatible. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] [...] there is what I call the "roundtrip fallacy": it is a mistake to use, as journalists and some economists do, statistics without logic but the reverse does not hold: It is not a mistake to use logic without statistics. — N. C. Taleb, Fooled by Randomness, 2004.

6 21

[asdf-devel] defsystem behaviour
by Serhiy Yakovyn 13 Sep '10

13 Sep '10

Hello all, I have discovered defsystem names systems in a bit opposite way defpackage does: (defsystem :some-system .) and (defsystem "some-system" .) define the same system, when (defsystem "SOME-SYSTEM" .) defines the other system. In contradiction, (defpackage :some-package .) and (defpackage "SOME-PACKAGE" .) define the same package, when (defpackage "some-package" .) defines the other package. Is this done intentionally? It would be good to point this difference in the documentation. Serhiy Y

2 1

[asdf-devel] Feature Request: Better Error Reporting
by Seth Burleigh 11 Sep '10

11 Sep '10

I was wondering if it was possible for some better error reporting. For example, when i was compiling kenny's cl-opengl, this is what i get: ; compiling (DEFVAR *OPENGL-DLL* ...) ; compiling (DEFUN CL-OPENGL-LOAD ...) ; compiling (CL-OPENGL-LOAD) ; compiling (DEFUN GL-BOOLEAN-TEST ...) ; compiling (DFENUM STORAGETYPE ...) ; compiling (DFENUM FILTERTYPES ...) ; /home/seth/install/lisp/cello/cl-opengl/sbcl-1.0.38-linux-x86/cl-opengl.fasl written ; compilation finished in 0:00:00.045 WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL {CB49DA9}> on #<CL-SOURCE-FILE "cl-opengl" {BD132C1}>. And then i get thrown into the slime debugger with a very nonhelpful error: compile-opp nil? Cant asdf give us the actual error thrown? This has happened multiple times on many libraries.

4 14

[asdf-devel] CMUCL error
by Devon Sean McCullough 06 Sep '10

06 Sep '10

Today's bleeding-edge ASDF fails to compile in CMUCL 1 compiler notes: ../asdf/asdf.lisp:3371:1: error: (during macroexpansion) Error in FDEFINITION: the function MODULE-COMPONENTS-BY-NAME is undefined. Compilation failed. Peace --Devon /~\ \ / Health Care X not warfare / \ PS: compiles fine in ACL

2 1

[asdf-devel] spurious warnings patch for CMUCL
by Devon Sean McCullough 06 Sep '10

06 Sep '10

Fix two unreachable code removal warnings in CMUCL: diff -Bbdur old/asdf/asdf.lisp new/asdf/asdf.lisp --- old/asdf/asdf.lisp 2010-05-21 17:18:04.000000000 -0400 +++ new/asdf/asdf.lisp 2010-05-22 17:01:06.000000000 -0400 @@ -492,7 +492,7 @@ (let* ((specified (pathname specified)) (defaults (pathname defaults)) (directory (pathname-directory specified)) - #-sbcl (directory (if (stringp directory) `(:absolute ,directory) directory)) + #-(or cmu sbcl) (directory (if (stringp directory) `(:absolute ,directory) directory)) (name (or (pathname-name specified) (pathname-name defaults))) (type (or (pathname-type specified) (pathname-type defaults))) (version (or (pathname-version specified) (pathname-version defaults)))) @@ -734,7 +734,7 @@ (directory (pathname-directory p))) (when (typep p 'logical-pathname) (return p)) (ignore-errors (return (truename p))) - #-sbcl (when (stringp directory) (return p)) + #-(or cmu sbcl) (when (stringp directory) (return p)) (when (not (eq :absolute (car directory))) (return p)) (let ((sofar (ignore-errors (truename (pathname-root p))))) (unless sofar (return p)) Peace --Devon /~\ \ / Health Care X not warfare / \ PS: Is this a good venue for patches?

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel September 2010