<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">On 15 Oct 2022, at 3:00, Russell Sim wrote:</p>
</div><div class="plaintext" style="white-space: normal;"><blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><p dir="auto">But regarding the readme file being loaded at read time in the ASD file.</p>
<p dir="auto">This dependency is not track but it's required to build the package.</p>
<p dir="auto">This could be caught if the builds were hermetical, and this would also</p>
<p dir="auto">help with issues related other static files that are missing from the</p>
<p dir="auto">ASD file. At the moment it's just luck if anyone actually adds the</p>
<p dir="auto">:STATIC-FILE components needed by their system. Is there some way to</p>
<p dir="auto">help system authors avoid accidentally missing files? Since it looks</p>
<p dir="auto">like a pretty common pattern to load the long-description from a readme.</p>
</blockquote></div>
<div class="markdown" style="white-space: normal;">
<p dir="auto">This may be another place where the problem isn't an ASDF problem.</p>
<p dir="auto">If programmers using ASDF used conventional CI and testing facilities, then they would have a test that would check a fresh copy of their systems out of the repository and that would build it the same way that a user would build it.</p>
<p dir="auto">If users would build from the repo, and that repo contains the static file (as it always would), then the tests would pass.</p>
<p dir="auto">If users would build from some distribution structure, on the other hand, and the test script did the same thing, the test script should fail if the <code style="margin: 0 0; padding: 0 0.25em; border-radius: 3px; background-color: #F7F7F7;">:static-file</code> is in the system definition, but not in the distribution structure.</p>
<p dir="auto">I haven't had time to check the above claim, but I do recall getting errors with a system that had a <code style="margin: 0 0; padding: 0 0.25em; border-radius: 3px; background-color: #F7F7F7;">:static-file</code> component in its declaration, but where that static file had been deleted from the repository. If I recall correctly, ASDF errored on the missing static file. If I'm wrong about this, and systems missing static files build successfully, that's an error in ASDF, and we should have an issue for it and fix it.</p>
<p dir="auto">ASDF does not need to be extended to add machinery to solve problems that GitHub and GitLab actions or Jenkins already solve. For that matter, since programmers could use arbitrary distribution methods, it isn't really possible for ASDF to solve these problems. But finding bugs that come when building in a clean environment is a problem that these CI systems are already addressing.</p>
</div>
</div>
</body>
</html>