<div dir="ltr">On Tue, Nov 1, 2011 at 06:14, Ketil Malde <span dir="ltr"><<a href="mailto:ketil@malde.org">ketil@malde.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Max Bolingbroke <<a href="mailto:batterseapower@hotmail.com">batterseapower@hotmail.com</a>> writes:<br>
<br>
>> This is where it stranded the last time, IIRC. That sentiment makes me<br>
>> a bit uneasy; so you are the official maintainer of a package on<br>
>> Hackage, but you do not want to hear about it when it fails to compile?<br>
<br>
> Don't forget that some packages fail to compile on Hackage even though<br>
> they work fine, because e.g. they depend on a third-party C library<br>
> that is not installed, or depend on some other package that Hackage<br>
> cannot build.<br>
<br>
</div>True, in that case, it's harder to avoid getting one email every time<br>
you upload a new version. We should still strive to have stuff build on<br>
Hackage (e.g. installing C libs or fixing the ohter packages); if the<br>
build fails for one of these reasons, you never know if it fails for<br>
other reasons as well.<br></blockquote><div><br></div><div>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.</div>
</div><div><br></div>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>wandering unix systems administrator (available) (412) 475-9364 vm/sms<br>
<br>
</div>