Some lisp applications (e.g. StumpWM) have problems with this older version of clx, so pull the upstream used by Quicklisp.
poudriere testport: Ok
I have spend more time and I now see that you intend for users to load etc/asdf-init.lisp in the startup script for their CL implementation and that file loads each CL's internal asdf.
I will hold off committing this for some time, because I would prefer to follow their releases instead of commits. One issue is that, even though their code is newer, it's version lower than our current version. I've submitted an issue to see if they will tag a new release, so we could avoid incrementing PORTEPOC.
Thanks. I agree (please see my last comment).
The problem here is that the current version in the tree is 0.7.4_1, even though the code from that upstream is older, seemingly unmaintained and has issues. I would like to switch to the more active upstream source, which is used by Quicklisp and avoid setting PORTEPOC, if possible.
pkg version -t 0.7.4_1 0.7.3.14 >
Now that I have received a positive response from the new upstream about tagging a new release, a simple DISTVERSION=0.7.5 should do.