Add version numbers #165; proposal#225
Open
mebenn wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've also had the same problem as mentioned in #165: to prepare a package for OpenIndiana/Illumos, some kind of versioning mechanism is required; but not the Git sha commit. So I added one, and found #165.
I've used MAJOR.MINOR.PATH; but maybe a major and minor is enough?
These are implemented as defines because we can use #ifdef, .. in the code to accomodate code changes. i.e.,, breaking API modifications, support for different GDB versions, ...
Added a new option '-v' (--version) and the version appears with -h.
I've also used this as the version number 0.9.1; but this is a completelly random sellection. What version should I change this to read? and please advise about the implementation.