[Openmcl-devel] ccl 1.11 release and GitHub
Bill St. Clair
wws at clozure.com
Tue Feb 14 01:57:32 UTC 2017
On Mon, Feb 13, 2017 at 7:26 PM, R. Matthew Emerson <rme at acm.org> wrote:
> In the Subversion world, sure, we could tag an old release, and that would
> include suitable bootstrapping binaries and interface databases.
> In the git world, a tag (as I understand it) is essentially a pointer to a
> particular commit. It is still necessary to have suitable bootstrapping
> binaries that will work to compile the sources at that point in time. As a
> concrete example of what I mean by this, note that a current development
> ccl (i.e., 1.12-dev) can't build a ccl from the 1.11 sources.
This suggests a solution to me.
CCL would have two GIT repositories:
1) Source code, tagged with releases, branched with patches for particular
releases. Move its tag when you add a bug-fix patch to a release.
2) Binaries. Branched from the beginning with one branch per platform.
Tagged to match the source tags, but with unique names for each branch:
1) Tags: 1.9, 1.10, 1.11
2) Branches: darwinx86, linuxarm, linuxppc, linuxx86, solarisx86, windows
darwinx86: 1.9-dx86, 1.10-dx86, 1.11-dx86
linuxarm: 1.9-armcl, 1.10-armcl, 1.11-armcl
linuxppc: 1.9-pp, 1.10-pp, 1.11-pp
linuxx86: 1.9-lx86, 1.10-lx86, 1.11-lx86
solarisx86: 1.9-sx86, 1.10-sx86, 1.11-sx86
windows: 1.9-wx86, 1.10-wx86, 1.11-wx86
This would allow you to put the two directories side-by-side, and, on the
linux-like platforms, have symbolic links from the source directory
reference the binaries in the binary directory:
trunk/ # Source for master branch
lx86cl -> ../trunk-bin/lx86cl
lx86cl.image -> ../trunk/bin/lx86cl.image
lx86cl64 -> ../trunk-bin/lx86cl64
lx86cl64.image -> ../trunk-bin/lx86cl64.image
trunk-bin/ # Binaries for master branch
We could have a script to run in the source directory to create the
symbolic links from <dir>/foo to ../<dir>-bin/foo
One remaining issue is what to do with the header directories. We could
either just have everybody always download all of them with the source, or
put them with the binaries and use symbolic links from the source directory
to get to them in the binary directory.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel