[Openmcl-devel] moving Clozure CL to GitHub

Chris Hanson cmhanson at eschatologist.net
Sat Feb 11 17:24:58 PST 2017

On Feb 10, 2017, at 8:26 AM, Ron Garret <ron at flownet.com> wrote:

> My suggestion:
> 1.  Don’t store the binaries in the source tree.
> 2.  Separate the initial bootstrap case from the case where someone already has a working CCL on their system and wants to upgrade.
> 3.  In the case where someone wants to upgrade, write a CCL script that does the Right Thing.  Because CCL already has snarf-url built in this should not be hard.  I volunteer to write and maintain it.  The instructions for upgrading CCL should be: run upgrade-ccl.lisp.
> 4.  In the case where someone is downloading CCL for the first time there are two options: either bite the bullet and make it a two-step process, or write a Python or bash script that does the Right Thing.
> Personally I think making it a two-step process makes sense.  Most people approaching CCL for the first time won’t care about the sources, they will want it to Just Work.  So keep pre-built binaries on a server somewhere for first-timers and updates, and keep the sources free of binaries.

I concur. This seems to work just fine with SBCL, and as an added bonus the SBCL binary distributions are structured in a way that makes them easy to drop into /opt.

  -- Chris

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

More information about the Openmcl-devel mailing list