Re: Smalltalk source control

The way GNU smalltalk solves this is that you have all .st files checked in.
In order to create a pristine image, you start GNU smalltalk (gst) with an option to re-create the image sourcing in all kernel files.

The kernel files are installed to /usr/local/share/smalltalk/...

The files are checked in at http://cvs.savannah.gnu.org/viewcvs/smalltalk/kernel/?root=smalltalk

The advantage is that you always have the full source file.
The patches, as you introduced them, simply become diffs between revisions of the same source file.

So, while you are under heavy development, you will re-create the image several times a week.
And you save a stable copy away for later, or for switching between stable and unstable image.

gst takes a minute or two to re-build the image I think.

----- Original Message ----
From: davegriswold9 <[email protected]>
To: [email protected]
Sent: Monday, September 18, 2006 11:45:05 PM
Subject: [strongtalk] Smalltalk source control

                           Question for those of you who are familiar with contributing Smalltalk
 source in Squeak or other open source Smalltalks: 
 
 We are going to have a problem right off the bat with source control
 for  the Strongtalk/Smalltal k library code.  Anybody familiar with how
 this is done for Squeak?  
 
 Of course we can simply archive patch file-ins, but that is inadequate
 for real source control.  We may need some tools in Strongtalk to help
 support this, and it would be a good idea to start thinking about that
 now.
 
 -Dave