Generate cabal files from `haskell_*` rules
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 279
- Forks
- 93
- Avg merge
- 13d 11h
- Merged PRs (30d)
- 3
Description
This might be out of the scope of this repo, but I'm opening this anyways to know whether it has been considered and start a discussion.
The story is that we'd like to open-source some haskell parts of our bazel-built monorepo. Open-sourcing them means releasing them on hackage, which requires writing .cabal files for them, and it would be nice to have a way to partially automate this (so more or less the inverse of Hazel).
This could be eased by the fact that we could write a hpack's package.yaml file instead which means that we can just spit out some json instead of having to write a custom format.
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
The issue names no implementation files, tests, or entry points. Start by reviewing the existing haskell_* rules and the proposed hpack package.yaml and .cabal outputs, then establish the intended scope and whether this belongs in rules_haskell; done would require an agreed generation design and implementation boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100