Add a PackageTest that packages with too new cabal-versions are skipped
Open
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
We can use local+noindex repositories for that.
Contributor guide
Research direction
Start by locating the existing PackageTest cases and how they configure repositories. Use the suggested local+noindex repositories to model packages with cabal-versions newer than the running Cabal version, and verify that those packages are skipped rather than treated as failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100