On Sat, Jan 2, 2016 at 1:42 PM, Robert Goldman rpgoldman@sift.net wrote:
Right now, I find just getting the new CL-based tools to work everywhere is a slog. I've been spending all of my available ASDF time lately wrestling with added complexities that are "meta" to ASDF, leaving me with no time to work on ASDF itself. I'm not willing to add more cognitive burden or overhead.
Sorry -- I appreciate your work to improve the process, Kambiz, but ASDF has just turned, against my will, into an laboratory for developing a CL-based scripting system. I am absolutely unwilling to see it turn into a testing ground for the bleeding edge of distributed version control, as well.
I apologize for the trouble. It's notably my fault for not testing on Mac and Windows.
But note that the need to download plenty of up-to-date libraries for testing purposes existed before the minimakefile merge. For instance, test-program always depended on lisp-invocation, test-encodings depended on asdf-encodings, etc. — though the policy was to let the test "succeed" with a warning if the dependency was not found. Similarly, the release script asdf-builder depended on inferior-shell and all its transitive dependencies, even before the current refactoring. The new asdf-tools only makes apparent early dependencies that were previously latent in the asdf test and release toolchain — some of them since ASDF 2 days, most of them since the initial ASDF 3 prerelease (2.27).
I updated the README to explain that you may need to make ext again after you update ASDF.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org I too am into martial arts: pistol shooting, rifle shooting, cannon shooting, flame throwing, grenade launching, missile firing, atom bombing...