Dear CLers,
with ASDF 3.3.1 released and the syntax-control branch pending review,
there's not much left for me to do with ASDF before I actually retire.
Now I'm looking for hackers to whom to pass the torch of ASDF hacking.
It so happens that I seem to have introduced (probably with 3.3.0) a
regression that breaks static image dumping of workout-timer with
cffi-toolchain. If people are interested, I could do the entire
debugging session over Google Hangouts, from isolating the bug and
filing a bug report to writing regression test and submitting a merge
request. That would be a good way to introduce newcomers to ASDF
hacking. Having a public ask questions as I make progress would be a
good way to keep the video relevant. Is anyone interested?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
If there's a book you really want to read but it hasn't been written yet,
then you must write it. — Toni Morrison [same with software, —♯f]
Hello everyone.
I have a rather particular problem that I have so far not been able to
solve on my own without brittle workarounds. Specifically, I'm looking
for a way to ensure that the directory paths stored in the FASL cache
directory are, if possible, truncated according to some other path (by
enough-pathname or a similar facility).
The reason I want this is for Portacle <https://portacle.github.io/>.
The Portacle directory should be relocatable and you should even be able
to take it with you on a flash drive to run on other machines. However,
this usually means that the absolute position of the directory on the
file system will change, even if the Lisp files and FASLs within it
remain at the same relative locations.
I would thus like to stop ASDF from recompiling everything when the
directory is moved absolutely, and instead rely on paths relative to
Portacle's own "root" directory if possible.
My current approach involves setting
asdf/output-translations::*output-translation-function* to a modified
version that attempts to relativise the path as seen here
<https://github.com/portacle/config/blob/master/sbcl-init.lisp#L70>.
However, this sometimes leads to issues
<https://github.com/portacle/portacle/issues/62> as the translated path
might be relative and other components down the line seem to expect
absolute paths.
Any advice on how to proceed on this would be appreciated.
Sincerely, Nicolas Hafner
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/115https://github.com/zkat/chanl/pull/12
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
If instead of teaching other people what government should be and should do,
you'd teach yourself what government actually is and does do,
you'd be a libertarian.
