<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=""><div class="">If I may, would git-lfs (<a href="https://git-lfs.github.com" class="">https://git-lfs.github.com</a>) be an option for this? It stores large binaries outside the repository, and just uses pointers within to resolve them as necessary.</div><div class=""><br class=""></div><div class="">It would mean users need to have both Git and Git-LFS installed, but it solves the repository bloat issue, and lets things keep working pretty similarly to the current SVN setup.</div><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 10, 2017, at 7:22 AM, R. Matthew Emerson <<a href="mailto:rme@acm.org" class="">rme@acm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Feb 9, 2017, at 10:48 PM, Ron Garret <<a href="mailto:ron@flownet.com" class="">ron@flownet.com</a>> wrote:<br class=""><br class=""><br class="">On Feb 9, 2017, at 7:39 PM, R. Matthew Emerson <<a href="mailto:rme@acm.org" class="">rme@acm.org</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">I still have not come up with a brilliant idea to solve the problem of distributing bootstrapping images and interface databases for each of the supported platforms.<br class=""></blockquote><br class="">Can you explain why this is any more of a problem with git than it was with subversion?<br class=""></blockquote><br class="">Back when OpenMCL was still in CVS, the way to get a copy was a multi-step process.<br class=""><br class="">1. get sources (via checkout or via downloading a file, e.g., openmcl-src-0.12.tar.gz)<br class=""><br class="">2. get interface databases (so that stuff like (#_getpid) will work) by downloading, e.g., openmcl-interfaces-0.4.tar.gz<br class=""><br class="">3. get bootstrapping image (e.g., openmcl-darwinppc-bin-0.12.tar.gz) in order to have a lisp to compile the sources<br class=""><br class="">When we switched to Subversion, we were able to do two things:<br class=""><br class="">1. Check in interface databases and bootstrapping binaries<br class=""><br class="">2. (Ab-)use externals so that it is possible to get sources, interface databases, and bootstrapping binaries in a single command<br class=""><br class="">Subversion supports binaries fairly well: it can diff them and store deltas. Since it's a centralized system, it doesn't matter if the repository gets large, because checking out a working copy doesn't have to copy the whole repository.<br class=""><br class="">Git is less suited to storing binaries. It stores them whole (i.e., it doesn't diff them), and since cloning a git repository copies the entire repository, bloating the repository with binaries is a real concern.<br class=""><br class="">In summary, I think that having a one-command way to get a working CCL is a good feature. I have never liked the way we abuse externals to do that, but the get-ccl-with-one-command feature seemed valuable enough that it was worth it anyway.<br class=""><br class="">Ideally, I'd like to make it equally easy to get a working CCL when we're on GitHub. That's what I'm trying to figure out how to do. It may be that I can preserve a one-step way to get CCL. Or it might be necessary to a) get source and then b) get interfaces & bootstrapping image. I'm hopeful that GitHub releases will be a good enough tool for this.<br class=""><br class="">_______________________________________________<br class="">Openmcl-devel mailing list<br class=""><a href="mailto:Openmcl-devel@clozure.com" class="">Openmcl-devel@clozure.com</a><br class="">https://lists.clozure.com/mailman/listinfo/openmcl-devel<br class=""></div></div></blockquote></div><br class=""></body></html>