Determine how different sorts of file names should be normalized
@nightlark is already working on this.
Since Dec 22, 2024.
Assessment
This issue has not been assessed yet.
Description
Different file names need to be normalized to have good odds of finding a match in our datasets. Generally, these are centered around a few things:
- Removing identifiers for a specific version from files names
- Removing platform/architecture specific information from file/folder names
What needs to get done may vary based on the type of file:
- Linux shared libraries (file name needs normalizing to remove architecture and version identifiers)
- C/C++ headers, pkgconfig/CMake Config files (need to recognize common include file paths, including ones that specify a multiarch triplet or GNU triplet)
- Linux binaries (need to recognize common bin folder paths, including ones that specif a multiarch triplet and maybe GNU triplet)
- Language/Ecosystem specific - different languages or ecosystems like Python, Windows, NuGet, and macOS could require handling the above in ways that are different than Linux
- Dominant language
- Python
- Stars
- 20
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from llnl/dapper
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100