Track metadata in VERSION_INFO #581
Merged
Conversation
This file contains 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
which will remain mostly undocumented for now Also: document the various "version" constants
flavorjones
force-pushed
the
flavorjones-version-info
branch
from
631ef3d
to
bdefd49
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
New constants track additional metadata:
SQLite3::SQLITE_PACKAGED_LIBRARIES(boolean) true if the gem is using the packaged libsqlite3, false if system librariesSQLite3::SQLITE_PRECOMPILED_LIBRARIES(boolean) true if the gem is using precompiled packaged libsqlite3New constant tracking a potpourri of metadata:
SQLite3::VERSION_INFOThis should unblock #578