automate "cabal check" in ghc release process
Currently the release manager must run cabal check manually on each package to check for problems that might cause the packages to be rejected when uploaded to Hackage. This should be automated.
Ideally we would use a dedicated program to do the check because the cabal command line utility uses a stable version of the Cabal library but the latest version of the Cabal library often has additional QA checks.
This was the case for the ghc-6.10.2 release. Hackage rejected the upload of containers-0.2.0.1 with the message:
Unfortunately the language extensions 'DeriveDataTypeable', 'MagicHash'
break the parser in earlier Cabal versions so you need to specify
'cabal-version: >= 1.2.3'. Alternatively if you require compatability
with earlier Cabal versions then you may be able to use an equivalent
compiler-specific flag.This happened because this QA check is only implemented in Cabal-1.7.x, not in the stable version that the cabal tool currently uses.
Trac metadata
| Trac field | Value |
|---|---|
| Version | |
| Type | Task |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Build System |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture |