Git tags for releases

[Lucidiot]

Hi! I would like to create an Alpine package for epy, which has mobi as a dependency, so I also have to make a package for mobi. Alpine packages are usually not built from a Git reference as they could be with Arch packages for example, so we would need actual version numbers. Would it be possible to create, even retroactively, some git tags on the commits that were used to build the versions that are currently published on PyPI? Even a tag for just the latest release would be good enough. Tags make the link between a published release and a commit much more clearer.

Additionally, as it seems Arch users are also having trouble with getting mobi to Arch, some documentation on how the package is built would be appreciated; Alpine packages are built directly from the source, not with any prebuilt binary. Even something as small as this would make my job easier!

[titusz]

I added a tag for the latest release. I also added a GitHub workflow that demonstrates how the package is built: https://github.com/iscc/mobi/blob/master/.github/workflows/build.yml

Does that help?

[Lucidiot]

That does help yes, thank you!

I'm now stuck because Loguru's tests are broken on Python 3.10 and that should be packaged before I can try mobi, but that's not really your fault 😅