This can work, but there is a problem if version.py continues to modify source controlled files. Changing any version controlled file committed or not in effect changes the version of the code being built, scm-version handles exactly this situation, it constructs unique versions for git tagged versions, commits beyond tagged versions, private commits and local changes to source files. This leads to the situation that re-executing the version/build process will generate successively different versions.
Placing the version into a build artefact outside of source version control avoids this instability in the version/build process. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-naming-scheme-for-tvm-versions-and-packages/6833/5) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/b755e77b738d968dbfe348713f4b33847c795f734e5a8666ce18d54c31626105).
