Meson can't determine version of pyshtools when installing from a source tarball about shtools HOT 5 OPEN

For downstreams, they can force the version for setuptools-scm with SETUPTOOLS_SCM_PRETEND_VERSION.

For generating a versioned file when running git archive, there's https://setuptools-scm.readthedocs.io/en/latest/usage/#git-archives though I'm not sure how that interacts with meson-python or setuptools-scm run at build time.

from shtools.

Here is a partial solution for the case where the tarball is generated by Meson : martinpitt/umockdev@cf0d7b4

To deal with the more generic case where the tarball is generated by git archive (or github), we would probably need to follow the approach as described in the above setuptools_scm git-archive docs.

from shtools.

And here is a PR that uses versioneer... #439

This mostly works, but as described in the PR, when run from a tarball, the version is set to '0+unknown'. This is better than not building at all, but I think that we can do better!

from shtools.