<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think that GitHub releases would work fine for this: there is mechanism there to upload big binary blobs as releases.<div class=""><br class=""></div><div class="">The only thing they probably are not suitable for is anything really long-term: GH will presumably evaporate within the life of CCL, so if really old binaries are ever wanted it's not an answer. But they probably will not ever be wanted except by mad future computer archeology people.</div><div class=""><br class=""></div><div class="">--tim</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 Feb 2017, at 18:25, Gail Zacharias <<a href="mailto:gz@clozure.com" class="">gz@clozure.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The one-step install is not the only issue. We have a self-bootstrapping system. If something breaks and isn't discovered for a while, it's useful to be able to back out of the broken binaries into an earlier version. So while github might not be the right place, the binaries do need to be stored and version-tracked somewhere, in a way that's correlatable with the sources.</span></div></blockquote></div><br class=""></div></body></html>