asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] pathname test
by Faré 16 Mar '10

16 Mar '10

This is invalid as a pathname to an actual file, only valid as something that you can merge with a pathname that has a type: (make-pathname :directory directory :name "typed-file.type" :type nil) Conversely, this is probably not a good idea for naming a file to load, as many implementations will add a type of .lisp or .lsp (or .fas) before trying to load such a file: (make-pathname :directory directory :name "untyped-file" :type nil) Or maybe they shouldn't? Not clear from the spec, but common practice is there. In other words, you need a different set of valid values for static-file and file components (though there might be a common subset). Can you work on the test as now part of the official testsuite? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] When everything seems to be going against you, remember that the airplane takes off against the wind, not with it. — Henry Ford

3 3

[asdf-devel] It's been fun, but my plate is full
by Nikodemus Siivola 16 Mar '10

16 Mar '10

On reflection I've decided to resign my ASDF commit bit. It's not like I've been doing much anything for ASDF lately, and I'm not even remotely on the ball when it comes to ASDF2. I'll probably lurk around on the mailing list still, though. Cheers, -- Nikodemus

1 0

[asdf-devel] ACL regression on latest ASDF
by Robert Goldman 16 Mar '10

16 Mar '10

ACL 8.1 and 8.2 now fail three tests, in both modern and ANSI modes: asdf-pathname-test.script test-module-pathnames.script test-utilities.script It /always/ failed test-utilities (there's a launchpad bug about this --- it's not clear to me that the test is right), but it used to pass all the rest. I think asdf-pathname-test is new, right? So maybe there's only the one regression. More as I get a chance to look into this. cheers, r

2 1

[asdf-devel] Tests now leave files behind
by Robert Goldman 16 Mar '10

16 Mar '10

I find that the tests don't clean up after themselves. The tests now leave behind .fasl files in ~/.cache/common-lisp/**/... This is not a directory structure I ever used before, nor is it one I ever intended to use. I /believe/ that the tests used to tidy up the fasls they created. I think either the ASDF fasl relocation facility should be turned off, or we need to provide a new clean up facility. I would prefer the former (except for tests that explicitly test the facility, preferably into /tmp rather than into the user's homedir). Best, r

2 4

[asdf-devel] Cache? Translations? How to get rid of them?
by Juan Jose Garcia-Ripoll 15 Mar '10

15 Mar '10

I must admit that after four hours fighting with this I am right now a bit pissed off, so please forgive the tone of the message. ASDF has introduced a new caching system which alters the names of all output files. This is making me mad because I am trying to implement pre-built ASDF components for ECL and ASDF insists on changing the value of output-files and input-files, looking for those prebuilt files at the location of the cache. What I have added so far is an extension to the system class, with hardcoded locations for prebuilt files (see below), so that I can store a single file $ cat ~/lib/ecl-10.3.1/serve-event.asd (DEFSYSTEM "serve-event" :CLASS ASDF::PREBUILT-SYSTEM :LIB "SYS:serve-event" :COMPONENTS ((:COMPILED-FILE "serve-event"))) Now the problem is that when I try to use these systems ASDF insists on translating the library file pathname "SYS:serve-event" to a cached name which does not exist. I have tried adding a TRUENAME around the output of OUTPUT-FILES, so that the return value reflects the full path, but ASDF insists in changing the name. I have tried hardcoding a system location, like SBCL does, but ASDF insists on appending its own translation > (asdf::output-translations) ((#P"/Users/jjgarcia/lib/ecl-10.3.1/" #P"/Users/jjgarcia/lib/ecl-10.3.1/") (#P"/**/*.*" #P"/Users/jjgarcia/.cache/common-lisp/ecl-10.3.1-darwin-x86/**/*.*")) Is there no rational way to prevent the translation of system directories without breaking the cache system? (defclass prebuilt-system (system) ((static-library :accessor prebuilt-system-static-library :initarg :lib))) (defmethod output-files ((o lib-op) (c prebuilt-system)) (list (compile-file-pathname (prebuilt-system-static-library c) :type :lib))) (defmethod perform ((o lib-op) (c prebuilt-system)) (car (output-files o c))) (defmethod component-depends-on ((o lib-op) (c prebuilt-system)) nil) (defmethod bundle-sub-operations ((o lib-op) (c prebuilt-system)) nil) (defmethod bundle-sub-operations ((o monolithic-lib-op) (c prebuilt-system)) (error "Prebuilt system ~S shipped with ECL can not be used in a monolithic library operation." c)) (defmethod bundle-sub-operations ((o monolithic-bundle-op) (c prebuilt-system)) nil) -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

4 21

Re: [asdf-devel] never ending component relative pathnames
by Faré 15 Mar '10

15 Mar '10

On 14 March 2010 21:04, james anderson <james.anderson(a)setf.de> wrote: > > On 2010-03-15, at 01:36 , Faré wrote: > >> Dear James, >> >> is there a tarball I can download with enough stuff to replace those >> tests or yours? > > ? > the tests are all in the one asdf-pathname-test.lisp file. > The amazon host is down. Also, when I last glanced, it looked like you needed some subdirectory with test files. Can you send on the list a tarball with the .lisp, .sh, and any ancillary file or does your script already create the files? > if the pathname reference failed, the entry looks like > > CL-SOURCE-FILE "file" > missing: #P"/ebs/test/asdf-src/system1/module1/ > untyped-file.lisp" > configuration: (#P"ASDFTEST:system1;" > #P"ASDFTEST:system2;module4;" #P"/ebs/test/asdf-src/system1/module1/ > untyped-file") > parent pathnames: (#P"ASDFTEST:system1;" > #P"ASDFTEST:system2;module4;") > Does "missing" means that you tried that pathname in the end, and failed? i.e. in that case, you were expecting a .lisp type, when you're not providing one in an explicit pathname? We explicitly won't merge any type when a pathname object is specified, so that the user can override component-provided types. >> Also, why do you map :unspecific to nil in merge-pathnames* ? What >> issues does that solve? Isn't that against what we want? > > i changed it to pass no argument when no value is intended. > on this topic clhs/make-pathname -> 19.2.1 lets you down. > you need to attend to 19.3.2.1 [1], to which it appears lispworks > pays attention.[2] > Ouch. I had missed this section. What about I change merge-pathnames* to squash :unspecific if and only if the host is a logical host? >> Shouldn't we >> rather have split-name-type return type :unspecific more often? Maybe >> your function should compare namestrings instead of pathnames? > > the test does not explicitly "compare". it create the files, then > uses the component pathnames to try to write to them (or just probe > for directories), and then confirms that it found all the intended > files by checking their modification times. at least, that is what it > is supposed to do. > OK. --#f Nostalgia isn’t what it used to be.

2 2

[asdf-devel] never ending component relative pathnames
by james anderson 15 Mar '10

15 Mar '10

good evening; on the occasion of pushing de.setf.graphics down the wire, when i built it for ccl/sbcl i did an obligatory pull on asdf and observe that something changed in the treatment of modules' component relative pathnames. with the effect that it was no longer possible possible to build clx. the clx-0-7-4 version as (:relative) specification in module pathnames which ran afoul of the asdf changes. i applied the same tactic as i have previously found effective for source file components and was able to build. the diff [1] is posted with the graphics sources. on other semi-related matters, i can report, that i have now an s3 ami (linux-2.6.31+ubuntu++^3) with which i can boot an ec2 instance with all pieces in place to run the target lisp implementations. --- [1] : http://github.com/lisp/de.setf.graphics/blob/master/readmes/ asdf.diff

4 36

[asdf-devel] asdf-version
by Nikodemus Siivola 14 Mar '10

14 Mar '10

What's the update policy? On every commit? (Since we're using Git I think this is pointless.) On release? (If so, I would suggest appending -dev to it outside releases.) Something else? Cheers, -- Nikodemus

3 7

Re: [asdf-devel] ASDF 2 confusion
by Robert Goldman 14 Mar '10

14 Mar '10

The member of *features* that indicates new asdf is :asdf2 This is probably the source of the confusion. Probably need a section of the manual on this. If you (or anyone else) find infelicities in the manual, please post or launchpad bug with location info. I'm very pressed for time right now and need all the help I can get squishing manual bugs. Thanks! "Nikodemus Siivola" <nikodemus(a)random-state.net> wrote: >The manual talks about both ASDF-VERSION and "ASDF 1" vs "ASDF 2", but >doesn't relate the two. > >Is anything post 1.600 "ASDF 2"? Might I suggest to drop the "ASDF 2" >language from the manual in that case -- because it is just confusing. > >Cheers, > > -- Nikodemus > >_______________________________________________ >asdf-devel mailing list >asdf-devel(a)common-lisp.net >http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.

2 3

[asdf-devel] ASDF manual lisp installation directions
by Robert Goldman 14 Mar '10

14 Mar '10

Going over the manual to tidy it up, I was quite surprised to read this: The default location for a user to install Common Lisp software is under `~/.local/share/common-lisp/source/'. This seems /very/ odd. Why would I want to install software in a location 'ls' is going to hide from me? For conventional programs, I stick the source in ~/src and I put my executables in ~/bin. It wouldn't even occur to me to stick them somewhere where I couldn't find them without something like 'ls -a'. Furthermore, since I work on my lisp code most of the day, it wouldn't occur to me to hide them four levels deep behind a hidden directory. Do most lisp users stick things in ~/.local ? And if so, why???? Thanks, r

4 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel