asdf-devel July 2009

asdf-devel@common-lisp.net

14 participants
17 discussions

[asdf-devel] bug in new ASDF
by Robert Goldman 13 Jul '09

13 Jul '09

I see the following when I try to load an asdf system now: Error loading #P"/Users/rpg/clinit.cl": While searching for system `asdf-context`: `(MERGE-PATHNAMES systems/ /Users/rpg/lisp/asdf-install-systems/)` evaluated to `/Users/rpg/lisp/asdf-install-systems/systems/` which is not a directory. The problem with this error is that, in fact, that IS a directory: CL-USER(2): (probe-file "/Users/rpg/lisp/asdf-install-systems/systems/") #P"/Users/rpg/lisp/asdf-install-systems/systems/" I'm looking in sysdef-central-registry-search and the logic seems to be completely borked. It looks for a system definition and, if it doesn't find one, it assumes that the directory name is bad. I believe the logic should be: 1. Look at the directory and ensure that it exists. 2. If it does not exist, push it onto the bad list 3. Else merge in the system name and look for the system definition. The current logic merges in the system name first, so misdiagnoses. [I will now proceed to wrestle with git, which I am coming to loathe with a consuming hatred, in order to attempt to verify that my diagnosis is correct, and then send a patch. More soon.]

4 12

Re: [asdf-devel] asdf 1.354 ?
by Gary King 12 Jul '09

12 Jul '09

(cc'd to list) Hi Faré, My bad. I forgot that I had been working in a branch so my push of master didn't push out the new changes. I just fixed this and pushed a moment ago. Please let me know if your mileage still varies. On Jul 11, 2009, at 5:24 PM, Faré wrote: > 2009/7/11 Gary King <gwking(a)metabang.com>: >> You may be going crazy but your sighting of the 1.354 message isn't >> evidence >> for that possibility. >> >> I did send such a message earlier today. >> >>> http://www.mail-archive.com/asdf-devel@common-lisp.net/msg00057.html >> > Dear Gary, > > thanks for your answer. I can't see it on git, though. Did you commit > to cvs, and then a daemon will update git, or something? > http://common-lisp.net/project/asdf/asdf.git > > I wanted to update xcvb to use this "official" (I think) git repo as > asdf upstream instead of xcvb's own thingie, but I can't find asdf > 1.354 there. > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org > ] > A co-mathematician is a machine for converting cotheorems into fee. -- 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] Patch for ACL 8.0
by Jeff Palmucci 11 Jul '09

11 Jul '09

When loading the git version of asdf under ACL 8.0, you get the following worrying message: Warning: Nested reader conditional detected on #<FILE-SIMPLE-STREAM #P"/afs/csail.mit.edu/u/j/jpalmucci/repo-install/repo- install/../asdf/asdf.lisp" for input pos 52418>. The behavior of this feature of ACL changed between ACL 7.0 and 8.0 to be more in line with the intent of the ANS specification. You should examine the code in question to make sure it does what you intend. In ACL 8.0, (list #+allegro :allegro #-allegro #+foo :foo #-foo :default) evaluates to (:allegro) instead of (:allegro :default) as in ACL 7.0 and before. See the documentation for EXCL:*WARN-ON-NESTED-READER-CONDITIONALS* and EXCL:*SHARP-PLUS-DE-FACTO-STANDARD-COMPATIBLE* for more information. Here as a patch to fix the problem.

2 1

[asdf-devel] Guard against (push "/foo/bar" asdf:*central-registry*)
by Tobias C. Rittweiler 11 Jul '09

11 Jul '09

I think it's bitten pretty much all of us that we at least once tried to push a non-directory-designating filename to *CENTRAL-REGISTRY*. It's a common pitfalls for newcomers. Couldn't ASDF signal a warning when it encounters such a thing while grovelling through the registry? -T.

7 15

[asdf-devel] pushed version 1.354
by Gary King 11 Jul '09

11 Jul '09

I did not move the RELEASE or STABLE tags though... Sat, 11 Jul 2009 13:15:53 -0400 Gary King handle bad *central-registry* itmes; xcvb compat * Add two restarts (coerce-entry-to-directory and remove-entry-from- registry) and use them to guard against *central-registry* entries that are not directories. * add some XCVB goodness to aid in compatibility. Thu, 9 Jul 2009 12:05:31 -0400 Gary King Patch for XCVB compatibility from Fare -- 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] Fwd: can't compile-file then load asdf.lisp
by Faré 09 Jul '09

09 Jul '09

Apparently, it is incorrect to try to update ASDF from a system where an older version of ASDF has already been loaded from which some DEFUNs (e.g. SYSTEM-SOURCE-FILE) have since converted to DEFGENERICs. This means that if you have an old clisp from debian and try to use the newer ASDF, you're out of luck. As a remedy, could we prepend the defpackage in asdf.lisp with the following? (eval-when (:compile-toplevel :load-toplevel) (let ((package (find-package '#:asdf))) (when package (delete-package package)))) [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Instead of loving your enemies, treat your friends a little better. -- Edgar Watson Howe ---------- Forwarded message ---------- From: Sam Steingold <sds(a)gnu.org> Date: 2009/7/8 Subject: Re: can't compile-file then load asdf.lisp To: Faré <fahree(a)gmail.com> Cc: clisp-list(a)lists.sourceforge.net Faré wrote: > > If I grab the latest asdf.lisp from git and try to compile-file it the one I have comes from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/cclan/asdf/ and it compiles and loads just fine. > then load it, I get a weird error message. > > WARNING: DEFGENERIC: redefining function SYSTEM-SOURCE-FILE in > /dev/shm/tmp/fare/xcvb-0.320/dependencies/asdf/asdf.fas, was > defined in top-level > *** - ENSURE-GENERIC-FUNCTION: SYSTEM-SOURCE-FILE does not name a > generic function this means that you have defined a regular function (with DEFUN) and now are trying to redefine it with DEFGENERIC. since asdf.lisp does not do that, you, apparently, have this function defined somewhere else.

3 4

[asdf-devel] Making ASDF ready for XCVB.
by Faré 08 Jul '09

08 Jul '09

Dear ASDF maintainers, would it be OK to apply the attached diff to asdf in git? It creates a trivial build.xcvb and a trivial module definition for ASDF, so that ASDF can be included in builds that use XCVB (including a bootstrapped version of XCVB itself). [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] If all values are relative, then cannibalism is a matter of taste. -- Leo Strauss

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel July 2009