Conversation
Also changed the lsb_release call for DISTVER to get the release number not the complete release description. I think this makes more sense for most distributions.
Member
|
Hello, thank you for your contribution. However, chaniging the DISTVER string like this can have a lot of side effects. As we are working on refactoring the whole OS information gathering, I would like to suggest we leve the DISTVER calculation in your PR like it is. Thenk you very much for your contribution, Philipp |
Member
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
3 participants
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.
Also changed the lsb_release call for DISTVER to get the release number not the complete release description. I think this makes more sense for most distributions.