View Single Post
Old 10-15-2026, 03:44 PM   #8
Kayadelenium
Addict
Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.
 
Kayadelenium's Avatar
 
Posts: 255
Karma: 364036
Join Date: Jul 2026
Location: Planet Earth
Device: Kobo Forma
Quote:
Originally Posted by patrik
It would be helpful if --help started with showing version number.
Thanks for the suggestion. The version has its own option: kepubverto -V, or --version, prints it along with the build it came from.

Code:
kepubverto -V
kepubverto 0.2.0+99140b0
The part after the plus is the commit the binary was built from, so it pins down exactly which code you are running. --help lists -V among its options, so that is where it points you.

I am keeping the two apart on purpose: --help says how to use the tool, -V says which version it is. Many of the command-line tools I use every day split them the same way. cargo, rustc, git and curl do not show a version in their help; cargo -V, rustc -V, git --version and curl -V print it. epubveri and epubsana, kepubverto's sister tools, work the same way, so the version is found the same way in all three.

JSWolf: thanks, I would like to hear how it goes on your Kobo.
Kayadelenium is offline   Reply With Quote