April 2015 - asdf-devel - mailman3.common-lisp.net

[asdf-devel] ASDF 3.0.1
by Faré 08 Apr '15

08 Apr '15

Dear Lisp hackers, ASDF 3.0.0 was decidedly short-lived. Longer live ASDF 3.0.1! An undocumented feature of version-satisfies, since the early days of ASDF 1, was that it would reject a component that didn't exactly match the specified major version as well as otherwise be same or newer as specified version. Of course, this broke quicklisp's check for a newer ASDF when ASDF went from major version 2 to major version 3. Since the feature was undocumented, and that users don't seem to ask for it, whereas many power users are inconvenienced by it, I just removed it. A future maintainer of ASDF may extend the `(:version ,dependency ,minimum-version) pattern for specifying dependencies with a `(:version ,dependency ,minimum-version ,too-large-version) pattern that allows to specify an exclusive upper bound on compatible versions. This would allow finer specification of compatible version ranges than just a match on the major version. But I didn't implement it. I leave it as an exercise for whoever volunteers to replace me, since I'm definitely leaving active maintenance of ASDF and unwilling to implement new features, though I will still fix bugs until a new maintainer rises. PS: this fiasco also suggests that a new maintainer shall include some typical quicklisp usage as part of the automated test suite. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org When you are young you are afraid people will steal your ideas; when you are old you are afraid they won't. — David D. Friedman

2 1

[asdf-devel] add-cldir helper script
by Daniel Herring 08 Apr '15

08 Apr '15

Re: [asdf-devel] Alternate default lisp system location On Wed, 12 Mar 2014, Zach Beane wrote: > Is there some easy way, supported by ASDF, to make a system known to > ASDF if you have its pathname? I added the following function to my ~/bashrc shortly after migrating to the new ASDF config mechanism. add-cldir() { cfg="$HOME/.config/common-lisp/source-registry.conf.d/10-$USER.conf" grep $PWD $cfg || echo "(:directory \"$PWD/\")" >> $cfg } This could easily be converted to a standalone shell script and batch file, suitable for all major platforms. - Daniel

2 1

[asdf-devel] is there a built in way to prevent ASDF from trying to upgrade itself?
by Gary King 08 Apr '15

08 Apr '15

thanks, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

3 2

[asdf-devel] ASDF3, or Why Lisp is Now an Acceptable Scripting Language
by Faré 08 Apr '15

08 Apr '15

Dear Common Lispers, I've submitted this article to ELS 2014. Happily, the deadline has been extended by two weeks, which leaves me time to rewrite it better, with your feedback. Can some of you proofread the article, both/either at a low-level and a high-level? I feel I didn't tie the parts of the article together enough, especially the end, that I rushed. What is worse, the limit is 16 pages, and I went overboard (NB: appendices don't count), so I'll have to cut stuff or move it to appendices. The source code: https://github.com/fare/asdf3-2013/blob/master/asdf3-2014.scrbl The latest compiled versions: http://fare.tunes.org/files/tmp/asdf/asdf3-2014.html http://fare.tunes.org/files/tmp/asdf/asdf3-2014.pdf Is this article useful at all? What high-level questions would you like answered? Note how writing this article has led to a lot of improvements to ASDF and cl-launch in the last few weeks, and is driving some of the discussions currently on asdf-devel. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Every program has at least one bug and can be shortened by at least one instruction — from which, by induction, one can deduce that every program can be reduced to one instruction which doesn't work.

1 0

[asdf-devel] New status of Mac tests
by Robert P. Goldman 08 Apr '15

08 Apr '15

All passing, with the exception of test-stamp-propagation on ABCL. Grr! As before: TEST ABORTED: These two expressions fail comparison with EQUAL: (SANITIZE-LOG (RELOAD ASDF/DEFSYSTEM:DEFSYSTEM)) evaluates to ((:COMPILING :SYSTEM)) (QUOTE ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2))) evaluates to ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2)) Above backtrace due to this condition: These two expressions fail comparison with EQUAL: (ASDF-TEST::SANITIZE-LOG (ASDF-TEST::RELOAD ASDF/DEFSYSTEM:DEFSYSTEM)) evaluates to ((:COMPILING :SYSTEM)) (QUOTE ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2))) evaluates to ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2)) Will test on Linux and report results from there, too.

2 1

Re: [asdf-devel] ASDF walkthrough
by Mark Evenson 08 Apr '15

08 Apr '15

Excellent idea! Please let me know when you will be doing this. Currently, I would possibly profit from an explanation of the kinds of "transversal" ASDF does over the "system of systems" it needs to do, but that is not too sharply defined as a question yet. Tersely pecked on my Nexus 5 On Jan 3, 2014 8:10 AM, =?ISO-8859-1?Q?Far=E9?= <fahree(a)gmail.com> wrote: > > Dear Lisp hackers, > > I'm considering recording a walk through the ASDF sources. > > I'd like to have an interactive session over Google Hangout > with one or a few people, explaining the current code in asdf/defsystem > (i.e. not going into uiop, except to minimally explain what asdf uses). > That should take about 2 hours. > > To enjoy the walkthrough, you need to be somewhat fluent in Common Lisp, > and somewhat familiar with how to use ASDF, though not necessarily with > either extending it or hacking its internals. > > If at least one person is familiar with ASDF 2 and has questions, > that could be interesting, or that could be a separate session. > > Please respond me to this email (privately or publicly) if you're interested. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org > We are always in anarchy. But we pay a hefty price maintaining the illusion > that we aren't, and another one being misled by the illusion. >

1 0

[asdf-devel] New version of ASDF with enhanced Allegro test script
by Robert P. Goldman 08 Apr '15

08 Apr '15

I just pushed version 3.1.0.25 that contains a modified version of the test script dealing with tests of Allegro Common Lisp. I tweaked the configuration of ACL testing to more closely reflect the directory structure and executable naming as Franz ships their systems. Now you can configure by simply pointing the test script at an install directory (32- or 64-bit, conventional or SMP). If you have an existing test configuration, it should not be broken by this (please let me know if that's not correct), but going forward configuration will involve setting fewer environment variables. Cheers, r

2 2

[asdf-devel] ASDF 3.0.2 released
by Robert Goldman 08 Apr '15

08 Apr '15

With a great deal of patient instruction from Faré, I released ASDF 3.0.2 yesterday. It is far more stable, and provides a wider range of support, than its immediate predecessor. We encourage implementations to update their bundled versions of ASDF. Many thanks to Faré for years of hard work and inspiration in improving ASDF. I will continue periodic releases of ASDF as bugs are found and fixed, but expect (hope) that most of the heavy lifting has been done. Best regards, Robert P.S. if other implementation mailing lists should receive these announcements, please let me know directly, so that I can update my lists.

2 1

[asdf-devel] Request for hands-off asdf.texinfo
by Robert P. Goldman 08 Apr '15

08 Apr '15

I'm in the middle of editing this, and have reached a point of introducing new nodes. This means that merging any changes will likely be a nightmare. Unfortunately, the node structure is still messed up, and I'm unwilling to push changes until it's fixed. So please, if anyone's thinking about editing this, hold off until future notice. Cheers, r

1 0

[asdf-devel] CCL Windows: output from ccl:fasl-concatenate is "not a FASL file"
by Dave Cooper 08 Apr '15

08 Apr '15

So I'm trying to get the ASDF test suite running on Windows, and tracked this down as one of the failures for CCL (32-bit and 64-bit). (there were 5 failures out of 47 tests, I haven't looked at the rest yet). This can be replicated as follows (with files from https://www.dropbox.com/sh/jc2cqwpkp06dupm/7lgyRUdwZ5/cl/tests/simple ): [below, substitute ".../'" for your actual path to the test files]: > (lisp-implementation-version) "Version 1.9-r15765 (WindowsX8664)" > (compile-file ".../try1") > (compile-file ".../try2") > (ccl:fasl-concatenate ".../try.wx64fsl" (list ".../try1.wx64fsl" ".../try2.wx64fsl")) > (load ".../try.wx64fsl") ERROR: Not a FASL file. Does anyone recognize what might be going on? -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

1 0