search

wustho / epy

CLI Ebook (epub2, epub3, fb2, mobi) Reader
GNU General Public License v3.0
962 stars 52 forks source link

Git tags for releases #47

Open Lucidiot opened 2 years ago

Lucidiot commented 2 years ago

I am currently creating an Alpine package for epr, and would like to do the same for epy. This will require making a package for mobi first, so I already made a similar issue on their repo. The distro's maintainers are not really fond of just building a package from a Git commit reference directly, and would definitely prefer the usual Git tags to denote releases. This allows the package to download the contents of the repo at a specific tag, making it clear which exact version we are downloading, and preventing me from picking for example the wrong commit for a specific version and causing a mess.

Another nice advantage of using Git tags is that it is possible to use the Atom feed GitHub provides for releases to be notified of releases; that way, I know when you make a release, and I can upgrade the package accordingly.

I guess adding a git tag to the .mkpkg file could help with automating this. In the meantime, you can just create a git tag for the last version that was built and sent on PyPI and that would be enough to get me started with the packaging.

This issue combined with the mobi issue could help get Arch users unstuck as well (#41), and the added Git tags can also help them get a epy package, not a epy-git, which could be more stable.

wustho commented 2 years ago

Hello there, thanks a lot for helping! Yes, sorry about release tag, I haven't been diligent enough at doing it... Will try to do better regarding that...