Maybe the Right Thing™ might be to walk the set of all slashy subsystems in the original asd, and create the same set, with the same names and same dependencies, in the delivered asd—just precompiled as .fasl instead of .lisp. I'm not volunteering to do any of the work (until someday hired as a CL developer again, maybe). But as usual, I'm willing to consult wrt what the current implementation does and what I think it should be doing. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org “The Government is just the armed gang you're afraid would take over in the absence of Government.” On Sun, Oct 20, 2024 at 8:06 AM Kasper Gałkowski <kasgal@posteo.net> wrote:
My use case is very similar to what Jason Miller described[1] previously. I'm also using Nix to build ASDF systems, and turned to bundle ops after finding source registry and output translations configuration too hard to manage. I also had problems with symlink behavior, which are often used in Nix but are hairy in CL[2]. Anyway, I got stuck working on the right Nix-side representation of ASDF systems before being forced to deal with the mentioned slashy system bundling issues. But with other stuff that has come up, I've shelved the topic and sticked with the SR/OT solution for deployments. Let's see if I'll be able to revisit in 2025. When that happens, I'll post a fresh bug report/patches to gitlab. In the meantime, anyone descending down the Lisp+Nix rabbit hole, feel free to get in touch.
[1]: https://mailman3.common-lisp.net/hyperkitty/list/asdf-devel@common-lisp.net/... [2]: https://patch-diff.githubusercontent.com/raw/Uthar/nix-cl/pull/42.patch
-- -Kasper