llnl / llnl/dapper

Determine how different sorts of file names should be normalized

Open
#28 2 comments 0 reactions 1 assignee View on GitHub

@nightlark is already working on this.

Since Dec 22, 2024.

Dominant language
Python
Stars
20
Forks
4
PR merge metrics
No merged PRs in 30d

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.