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

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

[asdf-devel] (asdf:build 'foo)
by Faré 08 Apr '15

08 Apr '15

While we are bikeshedding, I feel that asdf:load-system is (1) still too long a name, and (2) not generic enough, in case I want to use ASDF for stuff that isn't loading code into the current image. Therefore I propose there be (asdf:build 'foo) as the shorthand for the new (as of ASDF3) operation build-op: (defun build (system) (operate 'build-op system)) Shorter to type, more generic, and if we commit that before 3.1.1, available under the #+asdf3.1 feature. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Your conscience never stops you from doing anything. It just stops you from enjoying it.

2 4

[asdf-devel] Small testing convenience pushed
by Robert P. Goldman 08 Apr '15

08 Apr '15

If you test on ACL with the many variations that Dave set up (thanks, Dave!), there is a new problem: you end up testing upgrade over and over and over and over, and it takes forever. This recent commit adds the ability to set ASDF_TEST_UPGRADE_LISPS, typically as a subset of ASDF_TEST_LISPS. If the variable is unset, it should not affect you (but this is not tested). Best, r

1 0

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

08 Apr '15

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.

2 2

[asdf-devel] Patch for UIOP/UTILITY:ENSURE-FUNCTION
by Mark Evenson 08 Apr '15

08 Apr '15

Without the attached patch, I believe the use of a function for output translations is hosed from post asdf-3.0.2 onwards. I think ABCL is the only implementation actively using the ability to specify an output translation as a function, as indeed Faré expressly introduced this for us. ABCL uses a specialized output translation to translate the location of FASLs for ASDF systems stored in jar files (like ABCL’s contribs) which can’t otherwise be expressed in the translation DSL. I have [committed an asdf-3.0.3.0.1 including this patch][r14583] to ABCL trunk, which I will sync in the near future to ASDF master if this is indeed the correct way to patch the problem. [r14583]: http://abcl.org/trac/changeset/14583 -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

1 0

[asdf-devel] New ASDF test failures
by Robert P. Goldman 08 Apr '15

08 Apr '15

CCL: package-system-test.script clisp: asdf-pathname-test.script package-system-test.script test-sysdef-asdf.script sbcl: package-system-test ecl: package-system-test.script test-bundle.script (expected) test-sysdef-asdf.script cmucl: package-system-test lispworks: package-system-test I'm stopping for now -- it seems like package-system-test is now portably broken, at least on Mac OSX. Happy New Year, r

2 5