Numpy build requires writeable source directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, numpy
- Domain
- build-system
Research direction
Start by locating the NumPy package build definition and comparing it with the build rules for packages that already preserve pristine source directories. Reproduce the NumPy build, identify why it requests a writeable source directory, and verify that the build succeeds without modifying the source tree.
Written by the indexing model from the issue text.
Description
The numpy build needs to mark the source directory as writeable in order to perform the build. For every other package this has been avoided somehow, I would like to continue to treat the source directory as pristine.
- Dominant language
- Makefile
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
More from DiamondLightSource/rootfs
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
DiamondLightSource/rootfs#14 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
DiamondLightSource/rootfs#13 ·
All issues in DiamondLightSource/rootfs
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
Builders
Difficulty 2/5 1-3 hours Newbie friendliness 72/100