- Update output translations- Decouple ASDF initialization from devel/cl-asdf by creating a
- Ensure devel/cl-asdf is preferred over any ASDF bundled with Common
Lisp implementationsdedicated port: devel/freebsd-cl-asdf-init.
- Replace license text with an SPDX license identifier- Convert devel/cl-asdf/bsd.cl-asdf.mk to USES=cl.
- Simplify and clarify documentation- Add devel/cl-asdf-sbcl
- Do not assume ${PREFIX} is /usr/local- Update ASDF configuration:
- Remove the bespoke getenv function and use uiop:getenv - Prefer newer ASDF versions, but only if the fasl is available.
- Remove customization of asdf:output-files, which caused issues with - Replace license text with an SPDX license identifier.
output translation
A primary function of our ASDF initializ - Simplify and clarify documentation is to set up output.
translations. The previous approach had some issues:
- When users installed a Common Lisp port without the corresponding - Remove the assumption that ${PREFIX} is /usr/local.
FASL port, ASDF attempted to write the compiled FASL under- Use uiop:getenv instead of a custom getenv function.
/usr/local/lib/common-lisp/.
- The setup did not integrate well with Common Lisp code sourced- Remove asdf:output-files customization to resolve output
outside of ports, such as via Quicklisp.
With this update, output translations for a port are written only when issues.
the FASL port is also installed. This offers flexibility to users who - Improve output translations:
prefer build - Prevent writing systems at load time. They can install the Common Lispfasls to ${PREFIX}/lib/common-lisp/ when the
port without the associated FASL corresponding fasl port, and ASDF will revert to its is not installed.
default behaviour of storing FASLs to a cache under ${HOME}. - Fall back to ASDF's default caching mechanism of writing fasl to
a cache under ${HOME} when users install a Common Lisp port
without its fasl port.
- Improve interoperability with Common Lisp code from sources outside
of ports, such as Quicklisp.