[Openmcl-devel] moving Clozure CL to GitHub

Tim Bradshaw tfb at tfeb.org
Sat Feb 11 04:52:36 PST 2017

I think that GitHub releases would work fine for this: there is mechanism there to upload big binary blobs as releases.

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.


> On 10 Feb 2017, at 18:25, Gail Zacharias <gz at clozure.com> wrote:
> 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20170211/8bd1f23d/attachment.htm>

More information about the Openmcl-devel mailing list