<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 16 Jan 2018, at 14:17, Faré wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999">
<p dir="auto">:Robert<br>
In that case, it seems to me that<br>
check-not-old-asdf-system may be simply inappropriate as a check in some<br>
(all?) bundle operations. But I would be hard pressed to say when it is and<br>
is not appropriate. E.g., presumably it is appropriate in image building,<br>
since any image one builds would include the current running ASDF. But that<br>
argument does not seem to hold for bundles full of fasls or source code,<br>
does it?</p>
</blockquote>
<p dir="auto">Well, since at least on most implementations, building the fasls<br>
involve loading the code in the current image, there isn't much leeway<br>
by which asdf could afford not to use the same<br>
check-not-old-asdf-system function. A future version of ASDF that<br>
seriously supports cross-compilation might, but we're not quite there<br>
yet (see the TODO for hints, if you're interested in making it<br>
happen).</p>
</blockquote>
<p dir="auto">Am I correct in thinking that Dave's way of building monolithic bundles of either fasls or source code are, at least potentially, a baby version of cross-compilation? It seems like these are interesting <em>specifically</em> because they could be loaded into <em>different</em> images (otherwise, it's not clear to me why it would be better to build a monolithic FASL than just build an image).</p>
<p dir="auto">In that case, since this would effectively be cross-compilation (albeit a trivial case of it), it's not surprising that the logic for dealing with built-in dependencies like ASDF can go awry.</p>
<p dir="auto">In which case delivering with Docker might be the better approach! ;-)</p>
<p dir="auto">Best,<br>
r</p>
</div>
</div>
</body>
</html>