Fix installation/testing on Debian with OSSP::UUID #2
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
On Debian it's possible to install libossp-uuid-perl which provides a compatible Data::UUID interface. Historically I believe this was for license reasons but there are functional differences too like OSSP providing (and defaulting) to a version 4 (random) UUID which Data::UUID doesn't support. Becuase the version numbers are wildly different, not specifying our minimum version makes packaging a lot easier also because OSSP correctly produces a lowercase UUID as per the spec then our tests fail without an added uppercase. There's an upstream issue on Data::UUID tracking the mismatched case - bleargh45/Data-UUID#34
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.
On Debian it's possible to install libossp-uuid-perl which provides a compatible Data::UUID interface. Historically I believe this was for license reasons but there are functional differences too like OSSP providing (and defaulting) to a version 4 (random) UUID which Data::UUID doesn't support.
Becuase the version numbers are wildly different, not specifying our minimum version makes packaging a lot easier also because OSSP correctly produces a lowercase UUID as per the spec then our tests fail without an added uppercase. There's an upstream issue on Data::UUID tracking the mismatched case - bleargh45/Data-UUID#34
This PR is very similar to #1 but with the added
ucto make the tests pass on Debian under libossp-uuid-perl.