indygreg / indygreg/PyOxidizer
pyoxidizer temporary files placement
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
After https://github.com/indygreg/PyOxidizer/commit/5a36478710961 they will be placed near the binary, but sometimes it creates troubles.
For instance, when I need to pack this into brew formula I need to apply a hack - copy the binary to the tmp directory, since otherwise it will got EPERM error - https://github.com/Homebrew/homebrew-core/pull/157665/files#diff-9ee72002d07d6e92c8c603336e2241931cc327d3056543c40d2660ac3cd698e7R19
Maybe some env parameter to configure this behaviour?
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
Review commit 5a36478710961 to understand where temporary files are placed and how that behavior affects the Homebrew packaging case linked in the issue. Define a configurable placement mechanism that avoids the reported EPERM problem, then verify it against the packaging scenario described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100