asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[asdf-devel] how to query root of a system
by Tamas Papp 28 Oct '09

28 Oct '09

Hi, Suppose I have a library named MYLIBRARY which was installed in the directory /somewhere/foo/ (eg by ASDF-Install, clbuild or manually by the user). It has a /somewhere/foo/mylibrary.asd definition file, which was duly symlinked to mylibrary.asd in ASDF's central registry. The user can load it the usual way using ASDF. Is it possible to query the root directory somehow using the name? Eg I am looking for (query-system-root :mypackage) ; evaluates to #P"/somewhere/foo/" I could not find how to do this in the manual. Thanks, Tamas

4 4

[asdf-devel] tests failing
by Faré 27 Oct '09

27 Oct '09

I ran the tests for asdf. Out of 17, 5 fail on sbcl and 7 on clisp. Oops. On SBCL, the failures seem related to the pathname redirection of ABL / CLC. test1.script test2.script test3.script test-force.script test-static-and-serial.script On CLISP, the two additional failures are test-module-pathnames.script where clisp reads "foo.cl" as having directory nil instead of (:relative), which I think is legal, and test-retry-loading-component-1.script which seems to have to do with a restart-case retry in do-one-dep, but that's beyond my depth. The good news is most of these failures are only failures of the test themselves. The bad news is someone probably has to fix them and commit a fix. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Intentions are not so much direct descriptions of actual mind processes as Schelling points in the way social animals communicate.

2 4

[asdf-devel] announce: ASDF 1.368
by Gary King 27 Oct '09

27 Oct '09

thanks to Robert Goldman for some extension manual mucking! -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

Re: [asdf-devel] XCVB patch for split-sequence
by Faré 23 Oct '09

23 Oct '09

The cCLan list has apparently become the asdf-devel list. Is this still where the upstream for split-sequence is? If so, can this patch be applied? If not, who's in charge? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] "Politics" is made up of two words, "Poli", which is Greek for "many", and "tics", which are blood sucking insects. -- Gore Vidal

4 6

[asdf-devel] trac?
by Robert Goldman 22 Oct '09

22 Oct '09

Would it be acceptable to set up trac for ASDF? I just finished work on the manual for trac, and was going to take a look at some of the features issues that Nick Levine discovered, and it would make things much easier if some of these issues were available on a ticket system. Cheers, r

5 7

[asdf-devel] git docs
by Daniel Herring 21 Oct '09

21 Oct '09

For those seeking git mastery, or just trying to find their way out of a ditch, here's a couple more resources to look at. http://www-cs-students.stanford.edu/~blynn/gitmagic/ http://ftp.newartisans.com/pub/git.from.bottom.up.pdf Hope that helps, Daniel

1 0

[asdf-devel] ASDF test-op question
by Robert Goldman 19 Oct '09

19 Oct '09

I have been backporting Gary's markdown documentation to texinfo, and came across this: This operation should test the specified component. ASDF does not (currently) provide a method for returning a value from the test-op (or any other operation), so the implementor must ensure that executing test-op has the side effect of printing useful information about the tests to the CL stream *standard-output*. Question: do we want to specify *standard-output* as the destination for test-op output? I find that to be undesirable because on many CL implementations, it leads to test output being interspersed with lots of messages from compilation and loading, which makes it hard to find the test output you're looking for. I don't like specifying *standard-output* as the destination because it seems to me to be committing us to a bad solution. I think here /not/ specifying a destination is better than specifying a bad destination. I've never found a satisfactory solution to this problem. One suggestion would be to have the test-op take an init arg that specifies a stream (or a filename?) to which test output should be written. It would be left to test op implementers to figure out how to get their test output to go to that destination. I imagine this would typically be achieved by having the PERFORM method dynamically bind some variable that designates the destination. So, two proposals: 1. Delete the specification of *standard-output* as destination. 2. Add an initarg and slot for test-op and specify that output should go there. These are actually two somewhat independent proposals. A 'Yes' on 2 entails a 'Yes' on 1, but it's possible to say 'Yes' to 1 and 'No' to 2. Best, R

9 31

[asdf-devel] Announce : ASDF 1.367
by Gary King 19 Oct '09

19 Oct '09

commit bc11c0c786712020262239a95960c417c8c54547 Author: Gary King <gwking(a)franz.com> Date: Sun Oct 18 22:29:22 2009 -0400 update ASDF version to 1.367 commit 7ef572de9f2585ec5536fe212399afbd7bab2d4f Author: Gary King <gwking(a)franz.com> Date: Sun Oct 18 22:28:58 2009 -0400 safe-file-write-date and better symlink handling * Added and used `safe-file-write-date` to make things more self consistent * Made sure to use *load-pathname* and *load-truename* appropriately so that symlink resolution doesn't become a kerfuffle. commit 0be782a40ad9a98a4ece78306f8741921fb0e641 Author: Gary King <gwking(a)franz.com> Date: Wed Oct 14 09:27:46 2009 -0400 * add `asdf-extensions` package and start to flesh it out * apply patch to better handle relative source-file types (from Fare Rideau) * improve logic of tag updating in bump-revision-and-tag.sh * make test output nicer (from Fare Rideau) * improve test-module-pathnames (from Fare Rideau) -- 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] optimization settings
by Faré 18 Oct '09

18 Oct '09

While developing XCVB, I was reminded that when you declaim or compile-toplevel proclaim optimization settings, these settings may (ccl, allegro) or may not (cmucl, sbcl) persist beyond the compilation of the current file. To make the build deterministic, XCVB now resets the settings before every operation. And then I remembered that in building QRes at ITA, I had similarly had to reset settings around every system if not every file, so that one library's preferred settings would not pollute the build of each and every other subsequent piece of compiled code. The most directly relevant piece of code we use is as follows: (defmethod asdf:perform :around ((op asdf:compile-op) (system asdf:system)) (with-local-compilation-settings () (proclaim-optimization-settings-for system) (call-next-method))) (defmethod asdf:perform :around ((op asdf:load-op) (system asdf:system)) (with-local-compilation-settings () (proclaim-optimization-settings-for system) (call-next-method))) I tend to think that this should be around every component on not just systems (and that's what XCVB does) but in the above modification I was conservative. Would you agree to include code to this effect in the upstream ASDF? Otherwise, the effects of proclaim and declaim beyond the current file become implementation-dependent and that sucks, and/or people have to use declare (maybe locally) instead, which also sucks. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] A mathematician is a machine for converting coffee into theorems. [A co-mathematician is a machine for converting cotheorems into fee.]

2 1

[asdf-devel] loading component problem
by "Богдан Иванюк" 17 Oct '09

17 Oct '09

Hi, I'm using asdf-install over the clisp and have problem with loading already installed components. Thats looks like asdf and asdf-install successfully installed. This is my initialization file (~/.clisprc): #-:asdf (load "/home/bohdan/asdf/") (pushnew "/home/bohdan/asdf/registry/" asdf:*central-registry* :test #'equal) #-:asdf-install (asdf:operate 'asdf:load-op :asdf-install) I installed package cl-smtp with the next command: (asdf-install:install :cl-smtp) cl-smtp works after installation. After relaunching clisp can't load it: [1]> (asdf:oos 'asdf:load-op :cl-smtp) *** - component "cl-smtp" not found The following restarts are available: ABORT :R1 Abort main loop Also I can't load any file from ~/.asdf-install-dir/systems ... ~/.asdf-install-dir/systems$ ls cl-base64.asd cl-smtp.asd flexi-streams.asd mel-base.asd split-sequence.asd usocket.asd Can you help me with this issue? Maybe I do something wrong? Thank you. Bohdan.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel