diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2021-09-26 14:53:19 -0700 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2021-10-28 12:28:12 -0700 |
| commit | fa6cd2132d7e8e3e3dc5e817618c91052c7cb85e (patch) | |
| tree | feffa5061b4159afb25e5c4d321da4d8544b4deb /src/image.lisp | |
| parent | fbe55a361f4024464dedddd51715f3b560e702db (diff) | |
| download | consfigurator-fa6cd2132d7e8e3e3dc5e817618c91052c7cb85e.tar.gz | |
discuss limitations which apply to dumping images with IMAGE-DUMPED
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'src/image.lisp')
| -rw-r--r-- | src/image.lisp | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/image.lisp b/src/image.lisp index 28e1df1..0f136d5 100644 --- a/src/image.lisp +++ b/src/image.lisp @@ -287,7 +287,8 @@ then quietly skip over this property by applying it like this: ;; a remote Lisp image and every time we establish a further FORK-CONNECTION, ;; however, though perhaps we could arrange to avoid dumping an executable if ;; we know that we aren't going to need to reinvoke it, by having connection -;; types push hostattrs. +;; types push hostattrs. We would also need to resolve issues detailed under +;; "Dumping and reinvoking Lisp" in pitfalls.rst. ;; ;; If we took this approach, then we'd have implementation-specific dumping ;; code, but the code to reinvoke the dumped images would be fully portable -- |