feat: add Linux so file name normalization functions and example #31
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
Add functions for normalizing Linux SO file names, along with an example that uses the name normalization functions to look for Debian/Ubuntu file names installed by different packages that "collide" after being normalized. Addresses most of issue #5 regarding figuring out SO name normalization, other than deciding file names to check in other Linux distros and deciding if any other version numbers embedded in file names are worth trying to recognize (out of 39k SO file names, applies to <700).
nightlark
changed the title
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.
Mostly addresses #5, though limited to looking at Debian/Ubuntu package repositories. It probably isn't worth diving into package repositories for older releases, though as we get datasets for other Linux distributions that may influence how we normalize shared library file names.
There are additional ways we could try to extract version numbers embedded in the file names, but those likely apply to less than 700 out of 39k+ shared library file names in Debian/Ubuntu with many false positives -- so not worth pursuing at this time.