On Mon, Dec 11, 2017 at 2:13 PM, Faré <fah...@gmail.com> wrote: > ASDF needs volunteers to replace its retiring maintainers. > > One easy way to start, and a good filter for people non ready for the > job, is the simple and boring yet essential task of looking at > Quicklisp build failures and either fixing other people's build files, > or fixing ASDF, depending on who introduced the bug (often a > combination of the two). > > Recent Quicklisp build report: > http://report.quicklisp.org/2017-12-11/failure-report.html > > I've started these two pull requests: > https://github.com/marijnh/Postmodern/pull/115 > https://github.com/zkat/chanl/pull/12 Also https://gitlab.common-lisp.net/f2cl/f2cl/merge_requests/4
Here is another interesting breakage, that calls for an active new ASDF maintainer: https://github.com/Shinmera/qtools/issues/25#issuecomment-350873853 qt-libs tries to hot-patch commonqt to work around the way it builds and loads a C library, and ASDF 3.3 broke that. While a new set of workarounds is possible, a real fix, i.e. really teaching ASDF about C libraries, will require a maintainer with a good vision and the will to make things work --- and that's not me. Or you can all migrate to bazel. My offers to help a new maintainer get started still holds, so far. But my memory of ASDF won't hold indefinitely: > If there are candidate maintainers, we could do some more of these together. > This would build up: > * Good practice for dealing with build issues in quicklisp > * Knowledge of what is or isn't the contract provided by ASDF 3.3. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Those who hammer their guns into plows will plow for those who do not. — Thomas Jefferson
