I think we just use dependencies different things. This is a problem inherent in cabal.
When I (and others) specify a dependency, I'm saying "My package will work with these packages. I promise." When you (and others) specify a dependency, you're saying "If you use a version outside of these bounds, my package will break. I promise." They're similar, but subtly different. There are merits to both of these strategies, and it's unfortunate that this isn't specified in the PVP [1]. Janek: I've already given my method, and Peter has told you his method. Pick either, or make your own! Who knows, maybe someone else (or you!) will have an even better way to deal with this. :) - Clark [1] http://www.haskell.org/haskellwiki/Package_versioning_policy On Fri, Nov 9, 2012 at 1:03 PM, Peter Simons <sim...@cryp.to> wrote: > Hi Clark, > > > It's not restrictive. > > how can you say that by adding a version restriction you don't restrict > anything? > > > > I just don't like to claim that my package works with major versions > > of packages that I haven't tested. > > Why does it not bother you to claim that your package can *not* be built > with all those versions that you excluded without testing whether those > restrictions actually exist or not? > > Take care, > Peter > > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe