New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package detection #4
Comments
Possibly, but if I understand right, that would require the system to document be explicitly loaded after staple, yes? |
Indeed. |
Looks Good To Me. Congrats! (Well, I think the way you store the intermediate results is a bit distasteful, but, oh well.) |
I'm not happy with that either, to be honest. Any suggestions? |
No great suggestions, except that there should probably be separate tables for "packages we know have been created by this system" and "packages known to exist before this system". Especially since, when you load a system twice, etc., you may want to add to the first, rather than overwrite it — or else, the second time will erase all the information. |
Ah, yeah, I hadn't thought of that case. Fixed it now, though it won't be able to detect the case where you add a package through C-c C-c or similar, so it's still not flawless. |
Couldn't you use a
(defmethod perform :after ((o prepare-op) (s system)) ...)
and a(defmethod perform ((o load-op) (s system)) ...)
to record all the packages in existence before and after a system is loaded?The text was updated successfully, but these errors were encountered: