Considering that SBCL upgraded to 3.1.5 in July 2015, I think you should be pretty safe assuming that your users' ASDF is more recent than 3.1.4.
What more, even Xach seems to have miraculously seen the light: one months and one week ago, he updated the fallback ASDF in Quicklisp from 2.26 to 3.2.1! That was the first update of ASDF in Quicklisp since 2012, to a version then-current, to a version 4 years old. By linear extrapolation, we should expect the next update to happen in 2030, to a version from 2022. I admit that I was thinking his next move would be to downgrade ASDF to 1.369 (the last version before I took over). —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org To avoid criticism, do nothing, say nothing, and be nothing. – Elbert Hubbard On Thu, Mar 18, 2021 at 1:00 PM Didier Verna <did...@lrde.epita.fr> wrote: > > > Hi, > > I would like to remove some old workaround code from a couple of > systems, wrt to ASDF 3.1.4 bugs (see below). Is it safe to do so now, or > are these "bugs" still lurking around? > > The relevant parts are as follows: > > :defsystem-depends-on > (:net.didierverna.clon.setup/termio > #+sbcl ;; BUG in ASDF 3.1.4: d-d-o can't deal dependency expanding to NIL > (:feature :sbcl (:require :sb-grovel)) > #+(or allegro clisp lispworks) > (:feature (:or :allegro :clisp :lispworks) :cffi-grovel)) > > and > > :components (;; bug in ASDF 3.1.4: cannot deal with conditionally defined > ;; component class! > #+sbcl (sb-grovel:grovel-constants-file "sbcl/constants" > :package :net.didierverna.clon :if-feature :sbcl) > #+(or allegro clisp lispworks) > (:cffi-grovel-file "cffi/constants" > :if-feature (:or :allegro :clisp :lispworks)) > > Thank you!