I think there are some misunderstandings:
- hackage doesn’t enforce PVP at the moment anyway: it’s questionable whether the proposed change would have any real world impact, except for tooling that uses the PVP spec. It’s still recommending to use upper bounds.
- Actually, I find it highly questionable that the spec talks about ecosystem issues at all… and not only that, it also talks about a specific ecosystem. That makes it a poor spec. It’s a version spec and shouldn’t talk about how to handle your dependencies at all other than giving you expressive syntax to describe them
- hackage or any other ecosystem can easily enforce a superset of the spec. That’s entirely reasonable.
- Why would I use upper bounds on bytestring if all I’m importing is
pack? What is the reason to have the maintainer play whack the mole on upper bounds in this case?