repro_build_env_declared and repro_deps_pinned overlook native C/C++ build systems and toolchains
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the implementations of repro_build_env_declared and repro_deps_pinned, then read the referenced evaluation report for context. Check how they detect project files and produce verification guidance. Done means native build declarations and dependency manifests are considered for C/C++ projects, with relevant toolchain and ABI guidance.
Written by the indexing model from the issue text.
Description
Description
For projects containing C or C++ source code, repro_build_env_declared and repro_deps_pinned only look for container/script files and high-level package locks (npm, Python, Cargo). They completely ignore native build declarations (Makefile, CMakeLists.txt, CMakePresets.json) and native dependency manifests (Conan, vcpkg).
What We Did
- Audited a repository containing C code built via
Makefilewith toolchain variables (CC = gcc-13). - Ran
darnit audit . --framework reproducibility --show-all.
What It Was Supposed To Do
When C/C++ files are present, the tool should check for C/C++ toolchain declarations and native dependency manifests, or tailor the verification guidance towards compiler version pinning and shared library ABI stability.
What We Got
Both controls returned INCONCLUSIVE (WARN), directing the user only to check for Dockerfiles, Nix files, or language lockfiles like Cargo.lock or uv.lock.
Proposed Enhancement
- When native code (
.c,.cpp,.h) is detected in project context:- Check for CMake toolchain presets (
CMakePresets.json) or compiler definitions in Makefiles. - Check for C/C++ dependency managers (
conan.lock,vcpkg.json).
- Check for CMake toolchain presets (
- Provide verification steps relevant to native code (pinning system toolchain and libc versions).
- Dominant language
- Python
- Stars
- 22
- Forks
- 27
- Avg merge
- 2d 28m
- Merged PRs (30d)
- 40
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 darnitdevorg/darnit
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
darnitdevorg/darnit#589 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
darnitdevorg/darnit#587 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darnitdevorg/darnit#585 ·
Maintainers usually reply within 1 day
-
quality
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
darnitdevorg/darnit#523 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
darnitdevorg/darnit#516 ·
Maintainers usually reply within 1 day
All issues in darnitdevorg/darnit
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
gradio-app/gradio#13964 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
BSData/horus-heresy-3rd-edition#3232 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jbacalso24/mimry#123 ·
Maintainers usually reply within 1 day
-
p:3-mid pydanty:bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pydantic/pydantic-ai#10153 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue priority: medium size: S testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cubrid-lab/cubrid-cookbook-python#316 ·
Maintainers usually reply within 1 day