-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version checking uses wrong 'version' command #21
Comments
What's in place now is a workaround for this issue (looking at
I would assign this low priority, though when we update the binaries to new versions, we should then use |
If i understand correctly, this counts on the actual version string to come up on either I don't know how strong that assumption is... An alternative would be to explicitly define each binary's version command then use that. If it changes for any of them in future versions, we can update it to. It could be part of the refactor #27 |
I think that assumption is pretty good! You can see it work. I agree it's not elegant though.
Yes, then instead of handling two output types ( Improvement? I think this is low priority. |
The current version checking implementation for binaries assumes all binaries support the
--version
api.Some of them actually work with a
version
command/first arg.The text was updated successfully, but these errors were encountered: