-
Notifications
You must be signed in to change notification settings - Fork 16
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
Why buildnumber as versionnumber? #26
Comments
Hi, my understanding was that the build number is just an integer increased on every build publicly released, and the version is the semantic version (x.y.z), but I may be wrong.. are you recommending to use the semantic version also as the build number? It that's the common practice I'm ok with that. I'll look into it as soon as I have some time. If you are familiar with the common practice and can explain it to me here, I'd appreciate it :) |
Looks good, thanks. I bumped all three versions to 9.0.0, so that kext updaters see the version increase from both 9 and 2.5. Your updater may not detect this as a new version (if it considers 9 == 9.0.0), but there are no code changes anyway, so no need to update this time. Next version upgrade, it should pick it up. Correct me if I'm wrong. |
Hi cholonam.
Is it possible to put the Versionnumber instead of Buildnumber into the Info.plist? Normaly that is the regular way.
I´m the Author of the "Kext Updater" and it couldn´t detect it correctly because 9 is higher than 2.x and the users always get the message that the kext is the latest version and it is not.
The text was updated successfully, but these errors were encountered: