<div dir="ltr">The first step of the build process *checks* to see if the update script has been run (per comments I saw in a couple of files, actually running the update script automatically is problematic on one or two platforms) and fails if it hasn't. However, running the update script manually or automatically prior to running the build script is not an option building from the tarball since it's no longer a git repo (i.e. there is no version information to be found at that point and even if there were, the git tools which the update script depends on don't work with a bunch of loose files like this)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 18, 2021 at 4:21 PM Bruce O'Neel <<a href="mailto:bruce.oneel@pckswarms.ch">bruce.oneel@pckswarms.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Um, why doesn't the first step of make run the script that populates the SCCS version? It takes just a second or two.<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><div>On 2021-07-18T21:24:07.000+02:00, Phil B <<a href="mailto:pbpublist@gmail.com" target="_blank">pbpublist@gmail.com</a>> wrote:</div><blockquote><div><hr><div dir="ltr"><div dir="ltr">Jakob,<div><br></div><div>That appears to be how it's currently set up. The issue is that the updateSCCSVersions script is not being run before the tarball is generated to actually populate the placeholders. As far as I can tell, as a result there's no version information in the resulting archive. (i.e. <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/archive/refs/tags/202003021730.tar.gz" rel="noopener noreferrer" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm/archive/refs/tags/202003021730.tar.gz</a>)</div><div><br></div><div>For my purposes, the simplest solution would be if updateSCCSVersions were run immediately before generating the tarball. But I have no idea if that would cause problems elsewhere as that would depend on how the backend generating it is set up and/or what assumptions are being made by anything that might run after the tarball is generated.</div><div><br></div><div>Thanks,</div><div>Phil</div></div><br>
</div></div><div><div dir="ltr">On Sun, Jul 18, 2021 at 2:24 AM Jakob Reschke <<a href="mailto:jakres%2Bsqueak@gmail.com" rel="noopener noreferrer" target="_blank">jakres+squeak@gmail.com</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir="auto">Hi Phil,<div dir="auto"><br></div><div dir="auto">I think usually git-archive + smudge filters in .gitattributes for the version numbers are the solution.</div><div dir="auto"><br></div><div dir="auto">Is that an option here?</div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto">Jakob</div></div><br><div><div dir="ltr">Phil B <<a href="mailto:pbpublist@gmail.com" rel="noopener noreferrer" target="_blank">pbpublist@gmail.com</a>> schrieb am So., 18. Juli 2021, 03:04:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir="ltr">I am working on packaging up the VM for Debian and related distros. My current approach is to download the stable tarball release from <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest" rel="noopener noreferrer" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest</a>. The problem I'm having is that unless manual hacks are applied each time it is downloaded, the build will fail since platforms/Cross/vm/sqSCCSVersion.h has not been updated and the script to update it fails as the tarball is just a snapshot of the source files rather than a clone of the repo. (the snapshot is actually what is preferred vs a repo clone from a Debian packaging standpoint)<div><br></div><div>Ideally, the generated tarball would include a pre-updated sqSCCSVersion.h since this is a point in time snapshot. Is this something that makes sense and could be changed for the generated tarball? If not, any suggestions on how to handle this in an automated way for tarball builds? If I should be sourcing the tarball a different way, I'm open to that as well.<br><div><br></div><div>Thanks,</div><div>Phil</div></div></div>
</blockquote></div>
</blockquote></div></blockquote></div>
</blockquote></div>