Closed davidak closed 2 years ago
Sorry, versioning is hard on a personal fork.
The version format is uncommon, but not a problem for us. I ask for an option to show the version in terminal and exit.
I'm not sure if that fits for GUI programs and if it's a sane thing to ask. Do you have an opinion?
Otherwise we would need a GUI integration test, which can also be useful to make sure the GUI starts.
I see. The version string can always be found in README. Is that already what you need?
It could happen that a project forgets to update the readme, so that is not reliable.
I asked in social media if a --version
option makes sense for GUI programs, and everyone said yes. Many popular open source gui programs have that.
https://chaos.social/@davidak/108985098142325538
Would you implement that?
Please let me know if the latest release doesn't work as expected in your toolset.
It works perfectly! We will update the package in nixpkgs.
[davidak@gaming:~/code/nixpkgs]$ /nix/store/8sa86nrkyi01s516j0ng43wxwx6zs06k-vapoursynth-editor-19-mod-5.4-with-plugins/bin/vsedit --version
VapourSynth Editor R19-mod-5.4
Thank you!
I want to create an integration test to check if the packaged program has the right version. For that i need a way to output the version in terminal.
Most CLI programs have a parameter like:
vsedit --version
or
vsedit version
but both lead to error.
example:
Could you implement that feature?