Normalize package names
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading issue #5 and its linked comment, then inspect the repository's existing package-name handling entry points. Identify how versioned and development-suffix package names are currently represented before deciding how normalization should work. Done should include agreed handling for Ubuntu package cases and the llvm/gcc subpackage corner cases.
Written by the indexing model from the issue text.
Description
After looking at normalizing Linux shared library (.so) file names in #5 and looking at file names/package names for a bunch of stuff in Ubuntu package, there were a number of cases where package names contain a version number or dev suffix: https://github.com/LLNL/dapper/issues/5#issuecomment-2558282852
Some functions should be written to extract the version number from the package names in these cases and normalize them in some way to a name that doesn't contain version identifiers. This could involve mapping them to their source package name, though there are corner cases such as llvm/gcc which contain "subpackages" that would be better described as "libc", "libstdc++", or "clang" rather than the source package name (which might not even be llvm: it could be llvm-defaults or llvm-runtime).
- 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
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100