On Wed, Apr 9, 2014 at 10:47 AM, Michael Snoyman <michael@snoyman.com> wrote:

I don't read it that way at all. The PVP has two components: how to number your own packages, and how to place bounds on dependencies. That document says nothing at all about version bounds; it's referring explicitly to version numbers. You're doing this entire discussion a huge disservice by talking in absolutes like "doesn't obey the PVP."

The fourth bullet point in the first paragraph says explicitly: "We follow the Haskell Package Versioning Policy" and links to that document. I know you don't like it but please don't pretend like it isn't there.

Furthermore, I asked you for concrete examples of how enforcing a PVP requirement on tls would help the Haskell Platform; you responded with a document. I'm not interested in having a legal battle here; I'm trying to make sure we're making good technical decisions. So is there a reason to enforce this requirement on HP packages?

There are good reasons for following the package versioning policy as written, and this matter was debated when the policy was first proposed. We can debate it again (and we will, on the other thread), but this isn't about legalisms: packages that violate PVP break builds.

--
Gregory Collins <greg@gregorycollins.net>