[Openmcl-devel] How about Git?
dfigrish at gmail.com
Mon Nov 30 12:16:55 PST 2015
2015-11-30 22:49 GMT+03:00 Gail Zacharias <gz at clozure.com>:
> One approach I haven't seen discussed (so perhaps it has a fatal flaw I
> don't know about) is for distribution to be done via a tarball that
> consists of the binary distribution plus a skeleton version control tree -
> i.e. a source tree checked out the central repo, but with all the files
> deleted, so just the vcs meta-data. Installation consists of unpacking the
> tarball, and then (by hand or via a script) issuing the appropriate vcs
> command to fetch the latest sources, and finally rebuilding the images from
> source. By including the vcs meta-data in the tarball, you eliminate the
> failure mode of users not knowing where to get the sources, or getting the
> wrong version of the sources (although it doesn't eliminate the problem of
> users getting just the sources and not knowing how to get the binaries,
> which also used to happen, but that's more manageable).
I would prefer the installator for Linux (sh bundle), the installator for
the dmg for Mac OS X, the sources + binaries tarball, and the Git repo
which contains shell scripts for downloading appropriate binaries and hooks
which runs this scripts automatically.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel