When there is a revision like base <0, the hackage deprecation would only affect UI.
Let's make hackage smart enough to figure that out without a a deprecation.
As deprecation is also written to index, it's redundant information added there for no reason.
Semi-deciding out whether package has unjustifiable constraint should be easy:
look at library components condition trees top-level
E.g. there are issues like https://github.com/UnkindPartition/tasty/issues/426
When there is a revision like
base <0, the hackage deprecation would only affect UI. Let's make hackage smart enough to figure that out without a a deprecation.As deprecation is also written to index, it's redundant information added there for no reason.
Semi-deciding out whether package has unjustifiable constraint should be easy:
This information would make sense to calculate on upload and revisions.