Identify other package ecosystems of interest
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- docker (#50)
- npm
- www.jsdelivr.com or cdnjs?
- maven (#153)
- winget
- chocolatey
- homebrew
- vcpkg
- spack (#124)
- conan
- conda
- xrepo
- hunter
- cpm
- nix
- snapcraft
- flatpak
- https://mirrors.kernel.org/ - many Linux distributions
C++20 module name to package mapping
- Identify packages in apt, vcpkg, spack, source code repositories that export C++20 modules, and create a dataset mapping the exported names to the packages that provide an export with a matching name. Will require parsing source code to construct it.
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.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository structure and existing dependency-analysis tooling, then narrow the package ecosystems to support. Done means producing a dataset that maps exported C++20 module names to the packages providing matching exports, including the required source parsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker, linux, python
- Domain
- build-system, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100