[... and now to the whole list, I hate gmail's defaults... :-] ---------- Forwarded message ---------- From: Sven Panne <svenpanne@gmail.com> Date: 2015-11-29 21:12 GMT+01:00 Subject: Re: [Haskell-cafe] Fwd: Compatibility etiquette for apps, with cabal sandboxes and `stack` To: Imants Cekusins <imantc@gmail.com> 2015-11-29 20:52 GMT+01:00 Imants Cekusins <imantc@gmail.com>:
[...] What if the top package (in namespace) contained major version?
E.g. Cabal_1_22
below packages might use minor versions - basically, whenever api changes, change the version part of the affected package. [...]
As a developer, what should I import if my program/library works with e.g. the version range [1.20 .. 1.23]? It definitely can't be import Cabal_1_23.Foo.Bar because if it later still works with e.g. 1.24, I would have to rename all my imports. And always using the lower bound is probably too restrictive, unless I'm mistaken... In general I think it's a bad idea to spread build dependencies all over the code. Cheers, S.