Why upper bound version numbers?

[Brandon Allbery]

On Mon, Jun 6, 2016 at 8:19 PM, Dominick Samperi <djsamperi at gmail.com>
wrote:

> The odd thing about this is that to upper bound a package that you did
> not write (like base) you would have to know that incompatible changes
> were coming in subsequent revisions, or that features of the API that
> you rely on will be changed.
>

There is a versioning policy covering this. It has been found to be
necessary because otherwise people who try to build packages find
themselves with broken messes because of the assumption that any future
version of a package is guaranteed to be compatible.

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20160606/5000883d/attachment.html>