> > If the idea is to allow folks to not have to bother with CVS, it 
> > might be better to take snapshots of the CVS tree at known-stable 
> > times that correspond with specific released image versions.
> > 
> > If folks need the up-to-the-minute experimental stuff, requiring them 
> > to use CVS doesn't seem too onerous.
> Almost exactly the point I was trying to make. CVs appears to have all the
> basic capabilities to provide easy access to a 'certified' release in
> one go; I guess it would be nice to then archive each release in various
> ways for people not interested in using cvs. Archives with _everything_
> pre-generated as used for a release should be included.
> 

An additional issue is code generated from Squeak.  In addition to the
files from CVS, these releases should include things like interp.c . 
(If this sounds complicated, anyone, that's why we should have these
release files.  :))


-Lex