[Vm-dev] VM packaging for Cog transition

K. K. Subramaniam kksubbu.ml at gmail.com
Tue Nov 9 18:10:50 UTC 2010

On Tuesday 09 Nov 2010 10:30:17 pm Colin Putney wrote:
> On Tue, Nov 9, 2010 at 8:56 AM, K. K. Subramaniam <kksubbu.ml at gmail.com> 
> > A distributed version manager like git would be useful only for
> > hand-coded files. What about blobs like images, changesets and sources?
> How do you figure? Git or Mercurial can handle binary files as well as
> subversion.
Yes. but the history gets quite big with image blobs.

Bert's reply is ingenious ;-). Generated files are intermediate files, not true 
source files. True "sources" are actually Slang code in VMMaker image and these 
should be in version control.

When bootstrapping VM on a new platform, a sub-set of these intermediate files 
along with hand-coded source files are compiled generate a proto-vm. The proto-
vm runs VMMaker image to translate all Slang code into C so that the regular 
VM and plugins can now be built and the proto-vm can be discarded.

The VMMaker image is a critical part of bootstrap and should be put under 
version control.


More information about the Vm-dev mailing list