Re: [asdf-devel] 1.636

2010-03-16 Thread Mark Evenson
On 3/16/10 12:10 AM, james anderson wrote: most everything now has equivalent results.[1] abcl now loads asdf, but the test fails anomalously. looking... abcl fails in connection with a make-pathname operation of the sort (make-pathname :directory '(:relative) :name file :type

[asdf-devel] Patches for ABCL against asdf-1.641

2010-03-16 Thread Mark Evenson
Attached are patches in 'abcl-asdf.patch' to get asdf-1.641 to work against ABCL for the run-tests.sh. Unfortunately, you will need to build [ABCL from trunk][1] using at least svn r12550, because I had to patch ABCL to work with ASDF. And you'll need to apply the

[asdf-devel] ABCL trunk r12551 works with asdf-1.643

2010-03-16 Thread Mark Evenson
Thanks for applying my patches to ASDF, as it now appears that ABCL trunk (svn r12551 and later) runs pretty well with ASDF-1.643. The previous problem I noted with the binary locations getting collapsed was our problem which I fixed in ABCL. Attached is a (trivial) patch so that

Re: [asdf-devel] ABCL testing issue

2010-03-23 Thread Mark Evenson
On Mar 17, 2010, at 3:55 PM, ] wrote: http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/20100316T233422/abcl-output.txt Testing: test-force.script Armed Bear Common Lisp 0.18.1 Java 1.6.0_0 Sun Microsystems Inc. OpenJDK Client VM Low-level initialization completed in 1.985

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-24 Thread Mark Evenson
On 3/23/10 4:53 PM, Faré wrote: […] I hope ABCL has fixed its merge-pathnames woes. […] As I reported last week, ASDF2 works with ABCL from trunk and the upcoming abcl-0.19 release, for which I have fixed a couple issues with our pathname support. Are there current failures with ABCL's

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-24 Thread Mark Evenson
On 3/24/10 2:52 PM, Faré wrote: Sorry, I haven't tried recompiling the latest ABCL from source and don't know if any pathname issue remains. Have you tried downloading the latest ASDF and running its test suite? Do you pass all tests? I ought to include more tests about the

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-24 Thread Mark Evenson
On 3/24/10 4:54 PM, Erik Huelsmann wrote: Hi Alan, On Wed, Mar 24, 2010 at 3:36 PM, Alan Ruttenberg alanruttenb...@gmail.com wrote: Is ASDF2 what gets loaded when you require 'asdf in trunk, or some other action required to use it? -Alan I think we will need to update our ASDF now that

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-25 Thread Mark Evenson
)); +} } } }; diff -r a9813719dfba src/org/armedbear/lisp/JarStream.java --- /dev/null Thu Jan 01 00:00:00 1970 + +++ b/src/org/armedbear/lisp/JarStream.java Thu Mar 25 06:20:00 2010 +0100 @@ -0,0 +1,150 @@ +/* + * JarStream.java + * + * Copyright (C) 2010 Mark

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-25 Thread Mark Evenson
On 3/25/10 7:34 AM, Faré wrote: […] [1]: http://trac.common-lisp.net/armedbear/browser/trunk/abcl/src/org/armedbear/lisp/asdf-abcl.lisp Do you want me to merge that into upstream ASDF with #+abcl conditions? Not yet: it doesn't make sense until I figure out what works with ASDF2 (that patch

[asdf-devel] Patch for ASDF2 to use arbitrary output translation function

2010-03-25 Thread Mark Evenson
On 3/25/10 2:39 PM, Mark Evenson wrote: […] I'm working on an implementation of this on your git version as a proof of concept, but haven't gotten much further than getting your output configuration to accept the new syntax. I assume that actually applying the function will be easy, but I am

Re: [asdf-devel] [armedbear-devel] Patch for ASDF2 to use arbitrary output translation function

2010-03-25 Thread Mark Evenson
, Mark Evenson even...@panix.com wrote: On 3/25/10 2:39 PM, Mark Evenson wrote: […] I'm working on an implementation of this on your git version as a proof of concept, but haven't gotten much further than getting your output configuration to accept the new syntax. I assume that actually

Re: [asdf-devel] ABCL testing issue

2010-03-28 Thread Mark Evenson
On 3/17/10 4:15 PM, james anderson wrote: […] The specific bug you are encountering involves abcl-0.18.1 not being able to handle the renaming of a FASL, as ASDF2 compiles to asdf-tmp.XXX and then renames to asdf-LISP_IMPLEMENTATION.XXX. Rather embaressing for us, really, so [we fixed it

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-29 Thread Mark Evenson
On 3/29/10 8:25 AM, Faré wrote: Dear Mark, Fare's suggestion that I use an output translation based on the jar pathname doesn't quite work, because in our current implementation, the pathname of the jar is stored in DEVICE, separate from the rest of the jar pathname. I extended

Re: [asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

2010-03-29 Thread Mark Evenson
On Mar 29, 2010, at 10:39 AM, Faré wrote: […] So I would ask the ASDF developers to consider extending the output translation DSL to allow something like (initialize-output-translations '(:output-translations :ignore-inherited-configuration (#pjar:file:/**/*.jar!/**/*.*

Re: [asdf-devel] Patches for ASDF2 for translation function

2010-04-06 Thread Mark Evenson
On 4/5/10 8:59 PM, Faré wrote: Dear Mark, I merged your patch in, after rearranging it a little bit. Tell me how it's working for you... Seems to work just fine in my tests. Thanks for including this! -- A screaming comes across the sky. It has happened before, but there is nothing to

Re: [asdf-devel] translate-jar-pathname : The value NIL is not of type (OR PATHNAME STRING FILE-STREAM).

2010-04-10 Thread Mark Evenson
On 4/6/10 1:24 AM, james anderson wrote: given: [1] CL-USER(69): (lisp-implementation-type) Armed Bear Common Lisp [2] CL-USER(70): (lisp-implementation-version) 0.19.1 [3] CL-USER(73): asdf::*asdf-version* 1.666 asdf fails to compile alexandria. translate-jar-pathname applies namestring to

Re: [asdf-devel] translate-jar-pathname : The value NIL is not of type (OR PATHNAME STRING FILE-STREAM).

2010-05-01 Thread Mark Evenson
On 4/10/10 3:25 PM, Mark Evenson wrote: On 4/6/10 1:24 AM, james anderson wrote: given: [1] CL-USER(69): (lisp-implementation-type) Armed Bear Common Lisp [2] CL-USER(70): (lisp-implementation-version) 0.19.1 [3] CL-USER(73): asdf::*asdf-version* 1.666 asdf fails to compile alexandria

[asdf-devel] [bugfix] Fix ABCL loading ASDF definitions from jars under Windows

2010-05-01 Thread Mark Evenson
Attached please find a patch which fixes problems pointed out by Carlos Ungil when ABCL would catastrophically fail to translate the output location for ASDF systems located within jar files under Windows. We've fixed this in the version of ASDF 1.679 which we are planning to ship as part of

Re: [asdf-devel] [bugfix] Fix ABCL loading ASDF definitions from jars under Windows

2010-05-06 Thread Mark Evenson
On 5/1/10 9:26 PM, Faré wrote: Dear Mark, thanks a lot for your patch. Your efforts are appreciated. Not as much as I appreciate your unflagging energy (and time) towards shipping ASDF2. You will be missed after you ship this puppy! On 1 May 2010 14:04, Mark Evensoneven...@panix.com

Re: [asdf-devel] Fwd: Re: [Openmcl-devel] asdf 2 imported into trunk

2010-05-08 Thread Mark Evenson
On 5/8/10 1:05 AM, Faré wrote: I don't know the status of ASDF-INSTALL. It looks like ASDF-INSTALL is being maintained outside ASDF. We probably should remove the asdf-install and cclan files from our repository. Since ASDF-INSTALL has its own repository, they should probably #+asdf2 ify

Re: [asdf-devel] ASDF 2.003

2010-06-25 Thread Mark Evenson
On 6/24/10 11:51 PM, Faré wrote: Can ABCL upgrade its ASDF to 2.003 or whichever is latest in the release branch (if possible NOT the master branch)? That would be great. It should fix several bugs that may have hit ABCL users since then. Xach at least reported that upgrading ASDF on ABCL made

[asdf-devel] Disabling built-in output translation

2011-05-17 Thread Mark Evenson
ASDF contains some specialized code for ABCL that enable the translation of ASDF systems whose source is packaged into jar files to locate the corresponding object files in ASDF's user cache. In trying to figure out the correct mechanism to allow for binary ASDF distribution under ABCL that

[asdf-devel] ABCL packaging ASDF system in jars (was Re: Disabling built-in output translation)

2011-05-17 Thread Mark Evenson
On 5/17/11 3:28 PM, Faré wrote: […] Hope this helps. I'm gonna need a bit more time to chew over the ASDF code, but thanks for the general direction. I must confess that in spite of the reasonable looking documentation and having contributed the function translation code to ASDF, its whole

[asdf-devel] ASDF 2.016 breaks ABCL translations for jar files

2011-06-09 Thread Mark Evenson
Stellian's [normalization to ANSI semantics of COMPILE-FILE-PATHNAME*][1] has the unfortunate effect of breaking ABCL's translation of systems packaged in jar files. [1]: http://common-lisp.net/gitweb?p=projects/asdf/asdf.git;a=commit;h=ed4cd32932e937724b0b28d1c20ed6abe5d58dc0;js=1 I have

Re: [asdf-devel] ASDF 2.016 breaks ABCL translations for jar files

2011-06-09 Thread Mark Evenson
On 6/9/11 16:37 , Faré wrote: […] Can you write a simple test to be added to test/asdf-pathnames.script, I'll work on that. Can I just create a new top-level form or do you prefer I wedge it into TEST-COMPONENT-PATHNAMES with an #+abcl/#-abcl conditional? and/or send me an example such

Re: [asdf-devel] ASDF 2.016 breaks ABCL translations for jar files

2011-06-09 Thread Mark Evenson
On 6/9/11 6:44 PM, Faré wrote: Note that when I (describe #pjar:file:///foo/bar.jar!/baz/quux.lisp) I get: #Pjar:file:/foo/bar.jar!/baz/quux.lisp is an object of type EXTENSIONS:JAR-PATHNAME: HOST NIL DEVICE (#P/foo/bar.jar) DIRECTORY(:ABSOLUTE baz) NAME

Re: [asdf-devel] ASDF 2.016 breaks ABCL translations for jar files

2011-06-09 Thread Mark Evenson
On 6/9/11 7:06 PM, Faré wrote: Thanks for thinking with me on this. OK. I believe the following definition might make each of Stelian, you and I happy. Can you try it? (defun* compile-file-pathname* (input-filerest keyskey output-fileallow-other-keys) (if (absolute-pathname-p

Re: [asdf-devel] ASDF 2.016 breaks ABCL translations for jar files

2011-06-10 Thread Mark Evenson
On 6/10/11 00:57 , Faré wrote: On 6/10/11 00:57 , Faré wrote: Please try 2.016.1 and see if it satisfies you. Yes, that works for [ABCL and I have pushed][1]. [1]: http://trac.common-lisp.net/armedbear/changeset/13319 Pathnames are a big FAIL of CL. So thinks Stellian as well, so IOLIB

Re: [asdf-devel] ASDF 2.016 breaks ABCL translations for jar files

2011-06-10 Thread Mark Evenson
On 6/10/11 00:57 , Faré wrote: On 6/10/11 00:57 , Faré wrote: Please try 2.016.1 and see if it satisfies you. Yes, that works for [ABCL and I have pushed][1]. [1]: http://trac.common-lisp.net/armedbear/changeset/13319 Pathnames are a big FAIL of CL. So thinks Stellian as well, so IOLIB

Re: [asdf-devel] Disabling built-in output translation

2011-06-20 Thread Mark Evenson
On 5/17/11 15:28 , Faré wrote: […] Instead of disabling translations, you ought to add some specific translation (more specific than the default jar translation) that will tell ASDF that indeed for this or that jar, the fasls are stored in the jar, with an entry like: (:output-translations

[asdf-devel] Packaging jars in ABCL (was Re: Disabling built-in output translation)

2011-06-21 Thread Mark Evenson
On 5/17/11 15:28 , Faré wrote: BTW, for cl-launch and XCVB, I indeed am looking for a way to create bundles from compiled stuff. How do I create a jar from ABCL and a set of lisp files, precompiled or not? I've recently committed [ASDF-JAR which is a new contrib for ABCL][1] that should

Re: [asdf-devel] [armedbear-devel] asdf and windows vs unix on abcl

2011-10-20 Thread Mark Evenson
On Oct 20, 2011, at 18:00 , Faré wrote: ABCL is special in that it can run on either Windows or Unix. The problem is that ASDF 2.017 determines which of Windows or Unix at compile-time, which causes confusion when ABCL's builtin ASDF is compiled on Windows and used on Unix or vice-versa.

Re: [asdf-devel] asdf-bundle

2012-05-18 Thread Mark Evenson
On 5/3/12 17:55 , Faré wrote: asdf-bundle is now working (hopefully) on SBCL and CCL as well as ECL, by concatenating fasls. It won't work for systems where CFFI creates .so. Try it! (require :asdf) (require :asdf-bundle) (asdf:oos 'asdf::load-fasl-op :your-favorite-system) It creates a

Re: [asdf-devel] ECL tests failing on Mac OS X Lion [Re: asdf 2.23 released]

2012-07-24 Thread Mark Evenson
On 7/17/12 7:49 PM, Robert Goldman wrote: […] OK, I checked. This /is/ a bug with MacPorts, and they are working on it. I have a MacPOrts commit bit, so Lisp implementers should feel free to bug me with advice and/or patches… I'll take a stab at ecl-12.7.1 for MacPorts in the near future

[asdf-devel] Pre ASDF-2.27 failing to compile on ABCL

2013-01-15 Thread Mark Evenson
On 1/11/13 5:53 PM, Faré wrote: Dear Lisp hackers, I've completed yet another major pass of refactoring of ASDF. […] Coolness! Keep it coming! Failing to compiled the concatenated fasl from ASDF master tip (local : UNDEFINED-FUNCTION: ;COMMON-LISP:CELL-ERROR-NAME triggers autoloading

Re: [asdf-devel] [armedbear-devel] ASDF 2.29 released

2013-02-16 Thread Mark Evenson
On 2/16/13 4:08 PM, Faré wrote: Dear ABCL developers, ASDF 2.27 was a major rewrite of ASDF, and everything since then should be considered as candidate releases for ASDF 3: http://lists.common-lisp.net/pipermail/asdf-announce/2013-February/14.html ASDF 2.28 was released

Re: [asdf-devel] ABCL and UIOP

2013-03-26 Thread Mark Evenson
On 3/26/13 0039 , Faré wrote: Well, in this case, it looks like it's a bug in ABCL: [1] UIOP/BACKWARD-DRIVER(14): (find-symbol LOAD-ASDF-DEBUG-UTILITY :uiop/utility) UIOP/UTILITY::LOAD-ASDF-DEBUG-UTILITY :INTERNAL [1] UIOP/BACKWARD-DRIVER(15): (find-symbol LOAD-ASDF-DEBUG-UTILITY :uiop/driver)

Re: [asdf-devel] ABCL and UIOP

2013-03-26 Thread Mark Evenson
On 3/26/13 0039 , Faré wrote: Well, in this case, it looks like it's a bug in ABCL: [1] UIOP/BACKWARD-DRIVER(14): (find-symbol LOAD-ASDF-DEBUG-UTILITY :uiop/utility) UIOP/UTILITY::LOAD-ASDF-DEBUG-UTILITY :INTERNAL [1] UIOP/BACKWARD-DRIVER(15): (find-symbol LOAD-ASDF-DEBUG-UTILITY :uiop/driver)

Re: [asdf-devel] ABCL and UIOP

2013-03-27 Thread Mark Evenson
On 3/26/13 1733 , Mark Evenson wrote: I meant that I couldn't figure out how to reproduce the state you get ABCL into, but it seems the answer is that one tries to QL:QUICKLOAD :UIOP from abcl-1.2.0-dev. We managed to get this fixed in [ABCL][r14449]. [r14449]: http://trac.common-lisp.net

Re: [asdf-devel] [armedbear-devel] ASDF-JAR vs ASDF3 deployment support

2013-04-04 Thread Mark Evenson
On 4/4/13 12:44 AM, Anton Vodonosov wrote: […] General note about deployment CL systems. Often the deployment package should contain not only compiled code, but also resources: web libraries and frameworks often contain .css, .html, .javascript; bordeaux-threads uses version.lisp-sexp

[asdf-devel] Patch for UIOP/UTILITY:ENSURE-FUNCTION

2013-11-02 Thread Mark Evenson
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

[asdf-devel] Patch for UIOP/UTILITY:ENSURE-FUNCTION

2013-11-02 Thread Mark Evenson
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

[asdf-devel] Test for ASDF system in jar archive with ABCL

2013-11-06 Thread Mark Evenson
The ABCL contribs are all defined via ASDF in a jar file, so the test is simply to try to load one of them, here JSS. Not all downstream packaging systems include the abcl-contrib.jar, so I try to guard against a false negative with an UNLESS clause in the abcl-contrib REQUIRE, but in my testing

Re: [asdf-devel] Releasing asdf 3.1.1 ?

2013-12-19 Thread Mark Evenson
On Dec 19, 2013, at 17:20, Robert Goldman rpgold...@sift.net wrote: Faré wrote: Dear Robert, do you think we can release this year? All tests pass for me on Linux, and I believe all tests were passing for Dave Cooper on Windows. There has been very light development this past month, with

Re: [asdf-devel] Releasing asdf 3.1.1 ?

2013-12-20 Thread Mark Evenson
On Dec 19, 2013, at 17:23, Mark Evenson even...@panix.com wrote: […] I’ll take a look at the ABCL problem in the next day, reporting back to the list if I have a fix Unfortunately, I have come to the end of a long day for me without much to report as I have spent most of my non-work time

Testing ASDF with ABCL under Windows (was Re: [asdf-devel] Releasing asdf 3.1.1 ?)

2013-12-27 Thread Mark Evenson
On Dec 20, 2013, at 22:34, Mark Evenson even...@panix.com wrote: […] It isn’t quite clear how to run the tests under Windows. I am using Cygwin, so I thought I could just ensure that ‘abcl’ is in my path and symlinked to ‘abcl.bat cygwin-bash$ sh run-tests.sh abcl but I get

Re: [asdf-devel] ASDF walkthrough

2014-01-03 Thread Mark Evenson
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

Re: [asdf-devel] BUNDLE-OP now working on abcl-1.3.0-dev

2014-02-12 Thread Mark Evenson
On Feb 12, 2014, at 16:57, Robert Goldman rpgold...@sift.net wrote: Thank you very much, Mark -- I will get a micro-patch for this installed into ASDF for the new release. ASDF 3.1.0.65 works with ABCL trunk, which has just been committed as [r14626][]. Sorry that it is taking me so long

Re: [asdf-devel] asdf loading error error

2014-02-23 Thread Mark Evenson
On 2/23/14, 17:27, Robert Goldman wrote: Faré wrote: On Sat, Feb 22, 2014 at 3:26 PM, Cyrus Harmon ch-l...@bobobeach.com wrote: While trying to load and asdf system that generates an error (that’s another story, presumably an abcl-contrib problem), I get the following error: Error while

Re: [asdf-devel] proposal to split ASDF in half

2014-03-13 Thread Mark Evenson
On Mar 13, 2014, at 15:42, Robert P. Goldman rpgold...@sift.info wrote: […] I believe Faré and I discussed this issue in our first ASDF paper at ILC. For an even more radical proposal, see McDermott's earlier ILC paper about his chunking mechanism, which allows programmers to specify

Re: [asdf-devel] Alternate default lisp system location

2014-03-13 Thread Mark Evenson
I smell a need for a CDR, c'nest pas? Tersely pecked on my iPad On Mar 13, 2014, at 18:42, Faré fah...@gmail.com wrote: : dherring : sionescu : rpgoldman : sionescu For essential infrastructure like what ASDF claims to be, I expect major changes to happen less than once every 5 to 10

Re: [Asdf-devel] ASDF 3.1.2.9 now available

2014-07-18 Thread Mark Evenson
On 17 Jul 2014, at 04:43, Anton Vodonosov avodono...@yandex.ru wrote: I've run cl-test-grid tests on several lisps. No regressions detected. The lisps tested: abcl-1.2.1-fasl42-linux-x86 abcl-1.3.1-fasl42-linux-x86 abcl-1.4.0-dev has been updated to this ASDF. -- A screaming comes

Re: [Asdf-devel] startup times and initialize-source-registry

2014-08-21 Thread Mark Evenson
On 21 Aug 2014, at 02:36, Faré fah...@gmail.com wrote: […] The trick here is in this new stop-at-asd flag, which here defaults to t and isn't configurable, but which should default to nil and be configurable, for backward compatibility. Its effect is that recursing into subdirectories

Re: manual version

2015-04-03 Thread Mark Evenson
On 3/24/15 03:12, Robert P. Goldman wrote: DJ wrote: How do I know whether the asdf manual I am looking at matches the version of asdf I have installed? Seems like we should encourage the implementations to make the manual available to their users. ABCL has [always included the manual in

Re: manual version

2015-04-29 Thread Mark Evenson
On 2015/4/3 14:29, Robert P. Goldman wrote: Seems like we should encourage the implementations to make the manual available to their users. ABCL has [always included the manual in the source distribution][1]. Would you also like it in the binary distribution? [1]:

Re: ASDF configuration and cache

2015-04-29 Thread Mark Evenson
On 2015/4/29 10:03, Faré wrote: Dear Mark, ~/.config/common-lisp/source-registry.conf.d/ is being used because you're compiling on Unix. If you were using Windows, it would be using something else based on LOCALAPPDATA, not USERPROFILE. Hmmm. Do you mean compiling [ABCL] on Unix? That

Re: ASDF configuration and cache

2015-04-29 Thread Mark Evenson
On 2015/4/29 11:24, Faré wrote: On Wed, Apr 29, 2015 at 2:00 AM, Mark Evenson even...@panix.com wrote: On 2015/4/29 10:03, Faré wrote: Dear Mark, ~/.config/common-lisp/source-registry.conf.d/ is being used because you're compiling on Unix. If you were using Windows, it would be using

Re: ASDF configuration and cache

2015-04-29 Thread Mark Evenson
On 2015/4/29 07:13, Faré wrote: Dear Lispers, The most significant bit for this email is: DO YOU HAVE A source-registry.conf ON WINDOWS? or do you know someone who has? If so, please contact me, either on this list or in private, because I'm considering a backward-incompatible change in

Introspecting source registry

2015-06-07 Thread Mark Evenson
With asdf-3.1.4, how do I introspect the current state of source registry configuration? I need to debug a remote user's ASDF configuration on a machine which I don't have access to, so I would like to have ASDF output the current source registry configuration search state. Problematically, the

Understanding UIOP/RUN-PROGRAM

2015-09-29 Thread Mark Evenson
In a potentially memory constrained environment, I need to portably (across sbcl and ccl at least) process a potentially large (multiple GiB) stream of bytes output from a Linux command. For the curious, "process" here means encrypt with a block cipher and push to the network; whereas the UNIX

Re: Understanding UIOP/RUN-PROGRAM

2015-09-29 Thread Mark Evenson
On 2015/9/29 17:34, Faré wrote: > On Tue, Sep 29, 2015 at 11:03 AM, Mark Evenson <even...@panix.com> wrote: >> I wanted to confirm with ASDF developers that as far as I can tell from >> wrangling with UIOP:RUN-PROGRAM, it isn't going to do what I want >> because ther

Re: Simple (?) Windows question

2016-03-25 Thread Mark Evenson
On 2016/3/21 21:15, Robert Goldman wrote: > Is there some way that a CL implementation can know whether it is > running under a Unix-alike like Cygwin or MinGW? Another point to consider in finding the Right Thing here: Since ABCL runs on the JVM and the JVM is a Windows "native" executable,

Re: Recent disappearance of asdf:bundle-system.

2016-09-11 Thread Mark Evenson
> On Sep 11, 2016, at 08:31, Jean-Claude Beaudoin > wrote: > > Hello ASDF devs, > > I noticed recently that asdf/bundle:bundle-system has disappeared from ASDF. > MKCL is/was a user of that function as a convenient entry point to the ASDF > bundle facility.

Re: Misnamed secondary systems

2016-11-18 Thread Mark Evenson
> On 18 Nov 2016, at 14:40, Faré <fah...@gmail.com> wrote: > > On Fri, Nov 18, 2016 at 8:36 AM, Mark Evenson <even...@panix.com> wrote: >>> I'd like to forbid such misnamed systems. >>> Now a quick grepping through Quicklisp (see latest update

Re: Misnamed secondary systems

2016-11-18 Thread Mark Evenson
> On 18 Nov 2016, at 14:19, Faré wrote: > > Starting with ASDF 3 (2013), ASDF officially supports "secondary systems", > i.e. additional systems named in an asd, beside the main one. > For the additional systems to be findable by ASDF, though, their name > must be of the form

Re: Recent disappearance of asdf:bundle-system.

2016-10-16 Thread Mark Evenson
On 2016/9/11 17:09, Faré wrote: > 1- While the trivial convenience function bundle-system was removed, > the underlying functionality still exists. The function was ill-named > legacy of dubious value. Do ABCL users actually use this function as > such? [Sorry for the late reply] As far as I

Patch for ABCL development versions

2016-11-29 Thread Mark Evenson
I'm unsure of the current ASDF work flow for patch submissions, but I guessed that y'all would like [merge requests][57]. Without this patch, Elias' recent work on UIOP/RUN-PROGRAM won't be utilized on any ABCL which is built from development source. ABCL uses the convention that development

Is the :PERFORM stanza still valid?

2016-12-08 Thread Mark Evenson
If the perform stanza still the way to add operable test systems in ASDF? It would be nice to update the manual if this is not the case. For an ASDF test operation for a test system defined as: (asdf:defsystem plato-test :depends-on (:plato :prove) :components ((:module "t"

Re: Is the :PERFORM stanza still valid?

2016-12-08 Thread Mark Evenson
On 2016/12/8 18:28, Robert Goldman wrote: > Hi, Mark -- > > The issue is in PROVE-ASDF. Replacing line 50 of asdf.lisp > > (asdf:perform (make-instance 'asdf:load-source-op) c) > > with > > (asdf:perform (asdf:make-operation 'asdf:load-source-op) c) > > should solve the problem. > > LMK

Re: ASDF Best Practices

2017-03-31 Thread Mark Evenson
On 4/1/17 06:27, Faré wrote: > I've started an ASDF Best Practices document as a response to all the > ugly stuff I saw while debugging backward incompatibilities introduced > by ASDF 3.3. It is currently in my plan branch: > >

LOGICAL-PATHNAMES output locations

2017-05-22 Thread Mark Evenson
In spite of Faré's resistance to supporting LOGICAL-PATHNAMEs in ASDF, I would ask for help in using the current capabilities documented for ASDF-3.2. To wit, I would like to implement my own OUTPUT-TRANSLATIONS for LOGICAL-PATHNAMES [as is allowed (but discouraged)][1]. [1]:

Running asdf-3.3 aka 'plan' with ABCL

2017-05-16 Thread Mark Evenson
After a bit of analysis, I have [my first issue to report][1] with running asdf-3.3 (aka [the plan branch][2]) on [ABCL][3]. The problem stems from the new--and quite sensible--restriction that any [code in a ASDF:PERFORM cannot call into another ASDF:PERFORM operation][4]. QUICKLISP-ABCL's

Impact on modifying the current planning code (was Re: Plans for ASDF 3.3)

2017-05-04 Thread Mark Evenson
On 5/1/17 03:45, Faré wrote: > I took the content of this thread and edited it into a blog post: > http://fare.livejournal.com/188940.html > > Robert, can you tell me what the plan should be for ASDF 3.3, the > "plan" (phase separation) branch and the "syntax-control" branch? Thanks for the

Re: Impact on modifying the current planning code (was Re: Plans for ASDF 3.3)

2017-05-04 Thread Mark Evenson
On 5/4/17 18:41, Stelian Ionescu wrote: […] > ASDF currently (for Lisp) doesn't support >> a maximum version number, only a minimum. I keep meaning to fix that, >> but never get around to it. > > I believe this would be doubling down on the error of specifying versions in > ASDF. But as long

Re: Impact on modifying the current planning code (was Re: Plans for ASDF 3.3)

2017-05-04 Thread Mark Evenson
On 5/4/17 17:08, Faré wrote: > Dear Mark, > > thanks for your request. I'm not sure I understand how your ASDF > dependencies do or don't map to MVN entities, though. I also don't > understand the maven model very well. […] > > In case (a), it probably should be a special subclass of SYSTEM. In

Introspecting test suite passing/failing

2018-06-05 Thread Mark Evenson
We use ASDF to encapsulate the building and testing many systems under an automated test runner. For a given system, ASDF:TEST-SYSTEM always returns boolean truth as long as the invocation of the underlying test suite succeeds. This means there is no programatic way to provide a boolean as to

Re: Introspecting test suite passing/failing

2018-06-06 Thread Mark Evenson
> On Jun 6, 2018, at 19:14, Robert Goldman wrote: […] > If you get a chance, can you eyeball [my example code to try to use > FIVEAM-ASDF][2] to tell me if that looks like the correct usage? > > [2]: > https://github.com/emotiq/asdf-test-harness/blob/master/eg/fiveam-asdf-example.asd > >

Re: Introspecting test suite passing/failing

2018-06-06 Thread Mark Evenson
> On Jun 5, 2018, at 18:44, Robert Goldman wrote: > > I have pushed the system fiveam-asdf, which supports integration between ASDF > and the FIVEAM test library, to the contribs directory in the ASDF repo. > Please have a look. > > Be warned! It is old, and not being broke, hasn't been

Re: Introspecting test suite passing/failing

2018-06-06 Thread Mark Evenson
> On Jun 6, 2018, at 22:41, Mark Evenson wrote: > > > >> On Jun 6, 2018, at 21:08, Robert Goldman wrote: >> >> Will you please send me the example (with ancillary files), so that I can >> see exactly what's going wrong? > wget https://raw

Re: Introspecting test suite passing/failing

2018-06-06 Thread Mark Evenson
> On Jun 6, 2018, at 21:08, Robert Goldman wrote: > > Will you please send me the example (with ancillary files), so that I can see > exactly what's going wrong? […] Attaching wget https://raw.githubusercontent.com/emotiq/asdf-test-harness/master/eg/fiveam-asdf-example.asd -- "A

Re: Introspecting test suite passing/failing

2018-06-07 Thread Mark Evenson
> On Jun 7, 2018, at 00:21, Robert Goldman wrote: > > When I replaced fiveam-tester-system with :fiveam-tester-system or > "FIVEAM-TESTER-SYSTEM", the load went fine for me with the latest ASDF on > Allegro, SBCL, and ABCL 1.5.0. I must have been somehow introducing errors by being

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-06 Thread Mark Evenson
> On Apr 2, 2018, at 18:23, Robert Goldman <rpgold...@sift.info> wrote: > > On 1 Apr 2018, at 7:57, Mark Evenson wrote: > > On Apr 1, 2018, at 14:20, Attila Lendvai att...@lendvai.name wrote: > > The usage of DEFSYSTEM-DEPENDS-ON to specify dependenci

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-01 Thread Mark Evenson
> On Apr 1, 2018, at 14:20, Attila Lendvai wrote: > >> The usage of DEFSYSTEM-DEPENDS-ON to specify dependencies that will be >> satisfied by QL:QUICKLOAD no longer seems to be working in asdf-3.3.1. > > FTR, here's the history of this issue: > >

Problems with DEFSYSTEM-DEPENDS-ON

2018-04-01 Thread Mark Evenson
The usage of DEFSYSTEM-DEPENDS-ON to specify dependencies that will be satisfied by QL:QUICKLOAD no longer seems to be working in asdf-3.3.1. It used to be the case that to use the [PROVE testing framework][1], it was sufficient to place a … :defsystem-depends-on (:prove-asdf) … clause

Re: ASDF 3.3.3 is Released

2019-03-29 Thread Mark Evenson
> On Mar 27, 2019, at 17:49, Robert Goldman wrote: > > In honor of the impending 2019 European Lisp Symposium, today we release ASDF > 3.3.3, the third bugfix release for the 3.3 release series. > > We urge implementations that are currently bundling previous versions of ASDF > -- and