<div dir="ltr">ahhh ... makes perfect sense vis-a-vis the read/write problem Jeremy. Hopefully using an incremented version number is enforced via the hackage database!! ;^)<br><br>Vasili<br><br><div class="gmail_quote">On Fri, Aug 22, 2008 at 12:55 AM, Jeremy Shaw <span dir="ltr"><<a href="mailto:jeremy@n-heptane.com">jeremy@n-heptane.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">At Fri, 22 Aug 2008 00:29:40 -0500,<br>
<div class="Ih2E3d">Galchin, Vasili wrote:<br>
<br>
> 2) does the hackage database have a "reader/writer" lock to protect<br>
> readers, i.e. people downloading when I am uploading?<br>
<br>
</div> 1. new versions must have a different version number<br>
2. the version number is in the tarball name<br>
<br>
therefore:<br>
<br>
3. uploading a new version is a non-destructive operation and will<br>
not affect anyone downloading older versions.<br>
<br>
At least, that is my understanding.<br>
<font color="#888888"><br>
j.<br>
<br>
</font></blockquote></div><br></div>