On Tue, Nov 1, 2011 at 06:14, Ketil Malde <ke...@malde.org> wrote: > Max Bolingbroke <batterseapo...@hotmail.com> writes: > > >> This is where it stranded the last time, IIRC. That sentiment makes me > >> a bit uneasy; so you are the official maintainer of a package on > >> Hackage, but you do not want to hear about it when it fails to compile? > > > Don't forget that some packages fail to compile on Hackage even though > > they work fine, because e.g. they depend on a third-party C library > > that is not installed, or depend on some other package that Hackage > > cannot build. > > True, in that case, it's harder to avoid getting one email every time > you upload a new version. We should still strive to have stuff build on > Hackage (e.g. installing C libs or fixing the ohter packages); if the > build fails for one of these reasons, you never know if it fails for > other reasons as well. >
Instead of immediately sending mail, a daily process should pull up the most recent status for each package, grouped by maintainer, and send all the failures in a single daily message. Perhaps monthly this could be expanded to also report for the successful packages. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
