> On 8 Jun 2016, at 6:19 pm, Reid Barton <rwbar...@gmail.com> wrote: > > Suppose you maintain a library that is used by a lot of first year uni > students (like gloss). Suppose the next GHC version comes around and your > library hasn’t been updated yet because you’re waiting on some dependencies > to get fixed before you can release your own. Do you want your students to > get a “cannot install on this version” error, or some confusing build error > which they don’t understand? > > This is a popular but ultimately silly argument. First, cabal dependency > solver error messages are terrible; there's no way a new user would figure > out from a bunch of solver output about things like "base-4.7.0.2" and > "Dependency tree exhaustively searched" that the solution is to build with an > older version of GHC.
:-) At least “Dependency tree exhaustively searched” sounds like it’s not the maintainer’s problem. I prefer the complaints to say “can you please bump the bounds on this package” rather than “your package is broken”. Ben.
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
