keep enough information to reproduce a build without anod
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
when building a binary package with anod with should include all needed information so that we can reproduce a build without anod.
This includes the configure/build options. All environment variables that can impact the builds. And version of libraries/binaries used for the build.
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
Start by locating the anod binary-package build entry point and inspecting how build metadata is currently recorded. Determine how configure and build options, build-affecting environment variables, and library or binary versions can be captured without anod. Done means the recorded information is sufficient to reproduce the build independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100