NVIDIA / NVIDIA/hpc-container-maker
Question on boost.py: Why runtime instructions only copies boost-binary?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 517
- Forks
- 106
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
As boost relies on zlib etc, which is by default a dynamic-build, why we don't need to copy the ospackages stuff?
Contributor guide
No contributing guide indexed for this repository
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 reading boost.py and trace how its runtime instructions handle boost-binary versus ospackages. Compare that behavior with the issue's zlib and dynamic-build concern; the work is complete when the dependency-handling rationale is established and any required correction or documentation is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100