asdf-devel April 2017

asdf-devel@common-lisp.net

6 participants
3 discussions

Plans for ASDF 3.3
by Faré 16 May '17

16 May '17

Dear Robert, dear Lispers, I'd like to know what are the release plans will be for 3.3. My branch for proper phase separation is basically ready to be merged, but I'd like to see how compatible it is with next month's Quicklisp before I can recommend releasing it upon the masses. Note that the branch is called "plan" because it started as a refactoring how asdf builds its plan, but the changes run deeper than that — 970 lines were added or modified all over, not counting those moved around — that's double the number of lines of the original ASDF. Additional questions: should the syntax-control branch be worked on for 3.3.0? 3.2.2? 3.3.1? 3.4.0? It's a low-hanging fruit to making ASDF a more robust build tool that supports working with non-trivial syntax extension. PS: Are any (preferrably younger) lispers interested in becoming proficient at ASDF maintenance? There are plenty of TODO items of all sizes and all difficulties that could use some love. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org "I'm going to live forever, or die trying!" — Spider Robinson

6 22

ASDF 3.2.1 released
by Faré 04 Apr '17

04 Apr '17

It is with great pleasure that we announce the release of ASDF 3.2.1. This new release brings increased stability to the 3.2 series with many fixes to small issues since ASDF 3.2.0 from last January. Note that we already have significant changes in the pipeline and are still intending to release a 3.3.0 "in a couple of months". We urge implementations that are currently bundling previous versions of ASDF to adopt 3.2.1 at their earliest convenience. Release 3.2.1 contains significant bug fixes on multiple platforms and implementations, and does not introduce any incompatibilities on public APIs. It builds on 3.2.0, that did contain cleanups and refactorings that broke some previously undocumented (and sometimes explicitly deprecated) internals. Those systems in Quicklisp that used or abused these internals have been fixed (notably including slime, asdf-system-connections, cffi, iolib, prove, cl-protobufs). Details on bugfixes can be found at https://launchpad.net/asdf and in the discussions in merged branches of https://gitlab.common-lisp.net/asdf/asdf Notable credits go to Robert P. Goldman for continued testing, François-René Rideau for general coding and fixing a few more bugs than he put in, to Dave Cooper for lending access to a Windows test server, and to Anton Vodonosov for repeatedly testing with cl-test-grid. Here is the changelog entry for 3.2.1, compared to 3.1.0: cl-asdf (2:3.2.1-1) unstable; urgency=low New release: * source-registry: resolve conflicts in a way compatible with Quicklisp. * Upgrade: make the upgrade logic more robust, especially on CCL. * Require-system: better normalize module vs system names on CMUCL MKCL SBCL. * Logical pathnames: fix bad-system-name warning behavior when using LPNs. * XDG: skip empty entries, for compatibility with Ubuntu * Bundles: numerous fixes for bundles especially so for ECL and MKCL. Don't try to combine .a's as it's not portable; only ever combine but .o's. Getting rid of the *load-system-operation*, now it's always load-op. * launch-program: more fixes, notably for ECL, clasp. * Deprecation: fix issues with the deprecation schedule of some functions. * Test and Release: fixes to the release process and to a few tests. * Documentation: a document describing best practices when using ASDF. -- Francois-Rene Rideau <fare(a)tunes.org> Sun, 03 Avril 2017 14:49:29 +0100

2 2

ASDF Best Practices
by Faré 03 Apr '17

03 Apr '17

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: https://gitlab.common-lisp.net/asdf/asdf/blob/plan/doc/best_practices.md Early feedback welcome. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If a trainstation is where the trains stop, what is then a workstation... — Lars Lundgren <d95lars(a)dtek.chalmers.se>

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel April 2017