haskell / haskell/cabal

Allow specifying packages are successors / incompatible

Open
#11,629 6 comments 0 reactions 0 assignees View on GitHub
type: enhancement
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

**Describe the feature request**
Recently I forked the memory package as ram. This to end the basement/baseplate discussion by just ripping out basement from memory and other packages.

Now downstream users may get really bad error messages if they upgrade (crypton) for example. A type used from memory is incompatible with a type used from ram.
What I would like is to inform users that if the solver pulls in both memory and ram, something is going wrong. Instead of random compile or constraint errors.

This should make the community a bit more resilient against contactable but hostile maintainers.

**Additional context**
I decided to split it in this discussion: https://discourse.haskell.org/t/fork-basement-as-baseplate/12415/64

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.