libera/#commonlisp - IRC Chatlog

16:34:54 pve Josh_2: I made this a while back when I wanted to get *all* fasls required to load a system, are you trying to do something similar?

16:34:57 pve https://github.com/pve1/make-system-loader/blob/master/make-system-loader.lisp

16:36:30 Josh_2 Well when I connect so slynk server with sly-connect asdf goes off trying to compile files

16:36:40 Josh_2 so I'm not actually sure what I am trying to do yet

16:36:50 Josh_2 other than stop it doing that because the files dont exist

16:37:33 pve oh, ok nevermind then

16:37:49 Josh_2 Thanks for the suggestion

16:39:05 pve that thing in my link gathers up the fasls recursively and creates a lisp file that loads them, without asdf being loaded at all

16:59:38 NotThatRPG Josh_2: So what are the nonexistent files that ASDF is trying to compile? And what are the reasons for it trying to do this? What's the top-level call into ASDF that has kicked this off

17:00:03 NotThatRPG ACTION will be a bit slow answering....

17:00:12 Josh_2 asdf tries to find the .fasls for slynk

17:00:16 Josh_2 in .cache ... etc

17:01:30 Josh_2 I set it to immutable and then instead an attempt is made to read the files from quicklisp

17:01:39 Josh_2 idk. It might not be asdf doing it

17:01:48 Josh_2 I will have to check again

17:37:29 NotThatRPG Josh_2: I guess I don't see why ASDF isn't finding the slynk fasls. Isn't that the bug -- that you are running sly, and so slynk should be loaded and ASDF can't find it? Or is there something I'm missing

17:52:23 NotThatRPG Josh_2: Interesting -- I just checked my *sly-inferior-lisp for alisp* emacs buffer and indeed I see that at least some slynk files are getting recompiled. No idea why.

17:57:14 Josh_2 This is a problem :sob:

17:57:38 Josh_2 It means i have to move the cache into my container

17:57:48 Josh_2 But I dont see why it should be necessary

17:58:58 NotThatRPG No -- that was just because of an update to the lisp beta release. I started sly a second time and it just loaded the preexisting fasls.

18:01:21 NotThatRPG Josh_2: OK, maybe I'm starting to get the context -- you are running from inside a container, but are you bugged because the lisp is inside the container and the emacs is outside? I guess I don't see why you wouldn't have to put your fasl cache into the container. But... I don't know as much about interacting with a remote slynk server as I should. Never got it to work reliably myself.

18:01:47 NotThatRPG I assume that running in a container is basically the same as running on a different machine (which, as I said, I never got to work satisfactorily)

18:02:01 Josh_2 Basically yes

18:02:15 Josh_2 I dont see it needs to load the fasls anyway..

18:02:35 Josh_2 The whole system is pulled in as a dependency already

18:05:13 Josh_2 I could bundle the cached fasls with my image, and then when the image is deployed set the user cache

18:06:37 NotThatRPG So the problem is not that these are being compiled, but that you don't know why your image is loading the slynk server?

18:07:34 Josh_2 Well, I know what causes it.

18:07:46 Josh_2 When I connect to the listening server it loads the fasls

18:08:01 Josh_2 I suppose I can go ask on the sly github what the purpose of reloading these fasls is

19:20:47 NotThatRPG Josh_2: So what you are saying is that the image has the slynk server library preloaded, but when it gets a remote connection, it reloads them anyway?

19:21:33 NotThatRPG I can't say for sure, but it's equally possible this is a sly/slynk issue and not ASDF.

19:24:27 NotThatRPG Josh_2: I think it is slynk doing this. If you look at "start-slynk.lisp" (unless this has changed since my last pull), you will see an invocation of `slynk-loader:init` with the comment "reload SLYNK, even if the SLYNK package already exists".

19:24:39 NotThatRPG I don't know what the design rationale for that would be

19:27:39 pve perhaps it's related to the recompile-on-update mechanism that at least slime has (which doesn't use asdf)

19:57:44 Josh_2 Hmm

19:57:58 Josh_2 I wonder if I can make an issue and ask them to make it a configurable option

20:10:30 NotThatRPG Josh_2: The other thing you could do is change the fasl output mapping for the slynk libraries, and put only those fasls into your container. If I recall correctly there's a mapping that's sort of logical-pathname-like, and you can definitely carve out special places for particular fasls.

20:11:37 NotThatRPG Josh_2: See this section of the manual: https://asdf.common-lisp.dev/asdf/Controlling-where-ASDF-saves-compiled-files.html

20:12:44 NotThatRPG See the "CONFIGURATION DSL."

20:13:18 NotThatRPG I have to go now, but I hope that will put you on the right track. Ping me later if you need help.

22:43:09 xristos ** NICK Guest5402