Prevent .ghc.environment flags from getting picked up when running a @repl target.
Open
Nobody has claimed this yet.
good first issue
P3
type: feature request
- Dominant language
- Starlark
- Stars
- 279
- Forks
- 93
- Avg merge
- 13d 11h
- Merged PRs (30d)
- 3
Description
As per https://github.com/tweag/rules_haskell/issues/470#issuecomment-433845865 we want to make sure that https://github.com/haskell/cabal/issues/4542 does not taint our users repls with surprising behavior.
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 tracing how the @repl target is configured and where .ghc.environment flags enter the invocation, using the linked Cabal issue as context. Done means those flags no longer affect users' repls while the @repl target continues to run normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100