Why does the VM trunk download link on squeak.org point to github.com/opensmalltalk-vm rather than where the build artifacts are?
Because the readme.md has little badges you can click on:
Am 26.11.2021 09:29:03 schrieb Marcel Taeumel marcel.taeumel@hpi.de: Hi Eliot --
Run-specific artifacts (up to 90 days back) are here: https://github.com/OpenSmalltalk/opensmalltalk-vm/actions
The latest successful build artifacts are accumulated here: https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/latest-build
https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/latest-assert...
https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/latest-debug-...
Once we have a tag for a release candidate, one goes to each workflow and click "Run workflow":
Bset, Marcel Am 26.11.2021 06:36:59 schrieb Eliot Miranda eliot.miranda@gmail.com: Hi All,
where do the github actions built VM packages (e.g. squeak.cog.spur_linux32ARMv6_202111250841) end up? Why does the VM trunk download link on squeak.org point to github.com/opensmalltalk-vm rather than where the build artifacts are? _,,,^..^,,,_ best, Eliot
Hi All,
where do the github actions built VM packages (e.g. squeak.cog.spur_linux32ARMv6_202111250841) end up? Why does the VM trunk download link on squeak.org [http://squeak.org] point to github.com/opensmalltalk-vm [http://github.com/opensmalltalk-vm] rather than where the build artifacts are? _,,,^..^,,,_
best, Eliot