<div dir="ltr"><div><div><div>Actually, just a follow-up idea, what if cabal reported a link to this (or other) page whenever it fails?<br><br></div>It would be (one or two lines) more verbose, but it could be helpful from an usability point of view...<br>
<br></div>Just a suggestion,<br></div>Cheers<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-10 22:10 GMT+01:00 João Cristóvão <span dir="ltr"><<a href="mailto:jmacristovao@gmail.com" target="_blank">jmacristovao@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>> It might be good to also mention a user's options for using their own fork of a package ...<br>
<br>I was going to say: perhaps an Wiki entry stating what to do in case the build fails, but of course, it turns out there is one already:<br>
<br><a href="http://www.haskell.org/haskellwiki/Cabal/Survival" target="_blank">http://www.<span>haskell</span>.org/<span>haskellwiki</span>/Cabal/Survival</a><br>
<br></div>I would only add two steps:<br></div>1a) If the package has a <span>github</span> repository, check out if someone else already forked it (on <span>github</span>, not <span>hackage</span>) and check it out as a temporary solution or<br>
</div><div>1b) Do "cabal get -s package", and fix the package yourself, and...<br>
</div>2) with the use of cabal sandboxes, namely the "cabal sandbox add-source", the problem is easily solved.<br><br></div>I apply this most of the times I detect a package problem in parallel with notifying the author, and it has suited me well.<br>
</div><div>Perhaps its just a case of forwarding the users to this page?<br></div><div><br></div>Cheers<br><div>
<div><div><br><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-10 21:49 GMT+01:00 <span dir="ltr"><<a href="mailto:amindfv@gmail.com" target="_blank">amindfv@gmail.com</a>></span>:<div>
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>It might be good to also mention a user's options for using their own fork of a package while waiting for an update on hackage. Part of peoples' frustration seems to be coming from a feeling that they're blocked on waiting for the package to be updated.</div>
<div><br></div><div>Tom</div><div><br></div><div><br>El May 10, 2014, a las 15:35, Carter Schonwald <<a href="mailto:carter.schonwald@gmail.com" target="_blank">carter.schonwald@gmail.com</a>> escribió:<br><br></div>
<div><div><blockquote type="cite"><div>Let's update that policy with your and Edwards remarks?<span></span><br><br>On Saturday, May 10, 2014, Erik Hesselink <<a href="mailto:hesselink@gmail.com" target="_blank">hesselink@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sat, May 10, 2014 at 8:11 PM, Gershom Bazerman <<a>gershomb@gmail.com</a>> wrote:<br>
> I understand that Max did a bunch of very important work, then became<br>
> occupied with other things in the world. And in the long term, that needs to<br>
> be sorted out. But in the short term, a four-day-notice policy is silly. And<br>
> furthermore, even though there's nothing _wrong_ with forking promiscuously,<br>
> it tends to create a mess, to no good end.<br>
<br>
Just a small note since this was mentioned a couple of times: as<br>
hackage admins we don't have a 'four-day-notice policy'. The package<br>
takeover procedure [0] just says 'a while', and we've taken this to<br>
mean at least 2-3 weeks to account for vacations, other absences,<br>
general busyness etc.<br>
<br>
Erik<br>
<br>
[0] <a href="http://www.haskell.org/haskellwiki/Taking_over_a_package" target="_blank">http://www.haskell.org/haskellwiki/Taking_over_a_package</a><br>
_______________________________________________<br>
Libraries mailing list<br>
<a>Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</blockquote>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Libraries mailing list</span><br><span><a href="mailto:Libraries@haskell.org" target="_blank">Libraries@haskell.org</a></span><br>
<span><a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a></span><br></div></blockquote></div></div></div><br>_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org" target="_blank">Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
<br></blockquote></div></div></div><br></div>
</blockquote></div><br></div>