ASDF status for 3.1.7 release

Jens K. Loewe jens.k.loewe at
Wed Mar 30 15:31:29 UTC 2016

What was the precompilation step?

In general, I'd propose a Perl script for everything that involves
automatic file processing (it would even be easier to port it to Windows

Robert P. Goldman <rpgoldman at> schrieb am Mi., 30. März 2016, 15:02:

> The last time I tried it, the build process had been changed to require a
> precompilation step for the script runner, and that precompilation step
> failed for me.
> Prior to that the lisp-based solution seemed to mostly work, but was not
> maintainable by me. ASDF is all I can handle; I need to have a build system
> on which I can rely. Admittedly, bash is about the worst programming
> language short of INTERCAL, but I can trust bash and make, and there are a
> plethora of documentation and code sample resources.  I need that. I don't
> have the resources to beta test a new scripting framework as part of ASDF
> maintenance.
> So those are the symptoms of my allergy. Developing a scripting framework
> in CL is a fine project, it's just not MY project.
> Best,
> R
> > On Mar 28, 2016, at 18:15, Faré <fahree at> wrote:
> >
> > On Sun, Mar 27, 2016 at 6:05 PM, Jens K. Loewe
> > <jens.k.loewe at> wrote:
> >>> Going forward, we really need a Windows partner for ASDF.
> >>
> >> What would be required to fit in? I am still in the learning phase of my
> >> CL career, but I'm mainly using Windows for my every day tasks
> >> (including programming), so I might try.
> > Last I tried, the newfangled way of testing with asdf-tools worked
> > well on Windows. It triggers allergy in Robert, but you might want to
> > try it.
> >
> > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> > Conservative, n.:
> >      One who admires radicals centuries after they're dead.
> >              — Leo C. Rosten
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the asdf-devel mailing list