Testing that packages still compile

Mikolaj Konarski mikolaj at well-typed.com
Thu May 31 20:38:44 UTC 2018

You may also be interested in the "Hackage Matrix CI" links
on Hackage pages and the non-maintainer updates
of packages performed as part of the service to the community.

On Thu, May 31, 2018 at 11:32 AM, S├ębastien Hinderer
<Sebastien.Hinderer at inria.fr> wrote:
> Dear all,
> I am part of the OCaml development team. As you may know, OCaml has a
> package manager a bit similar to cabal whose name is opam.
> One of my colleagues spends quite a lot of time trying to make sure that
> packages still compile with a new version of the compiler, when we
> release it. When a package does not compile any longer, it seems it is a
> highly non-trivial task to figure out what exactly is broken: is it the
> package itself which has been broken by a change in the compiler, or is
> it one of its dependencies.
> I am assuming the same kind of problems occur with Haskell and am
> wondering how they are handle.
> Has there been something published on this kind of problem?
> Any pointer, comment or contact appreciated.
> Best wishes,
> S├ębastien.
> _______________________________________________
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users

More information about the Glasgow-haskell-users mailing list