RE: proposal for how to synchronize Strongtalk source

> -----Original Message-----
> From: [email protected] [mailto:strongtalk-
> [email protected]] On Behalf Of David Griswold
> Sent: Tuesday, May 08, 2007 8:38 AM
> To: strongtalk
> Subject: proposal for how to synchronize Strongtalk source
> 
> 
> Hi all,
> 
> Okay, I've come up with a proposal for how to solve the problem of how
> to
> synchronize people's images with the repository.
> 
> Basically the change log is the right place to start.  Right now the
> change
> log is not in the repository, other than in the base zip file for
> eventual
> bootstrapping.  First it needs to be added to the repository.
> Subsequently,
> changes to the Strongtalk-side code base will always be committed as
> appends
> to the change log.  The StrongtalkSource directory which currently
> holds
> discrete files for each class or entity, should be removed, to prevent
> problems synchronizing with the change log.
> 
> When people want to synchronize their image with the repository, they
> will
> need to check out the repository's change log in such a way as to not
> overwrite their current copy.  Then, I can write a small tool in
> Strongtalk
> that compares the two change logs, to find their common prefix.
> Everything
> after that common prefix in the repository change log, will be
> considered
> the incremental update to be applied to the developer's image, which
> can
> then be filed in.  This should cover the case where the tail of the
> developer's change log is different.  I believe that subversion's
> merging
> mechanism ought to be sufficient for dealing with integrating
> simultaneous
> changes to the change log.
> 
> I know that other Smalltalk's have more sophisticated change log
> mechanisms
> for this sort of thing; Strongtalk is quite primitive in this respect
> right
> now.  While I don't want to dedicate a lot of work to the Strongtalk
> side
> right now since we are going to be focusing on squeak for the near
> future,
> we still need something at least a little bit better on the Strongtalk
> side.
> 
> Let me know if anyone has a better idea.
> 
> Dave
> 
> 

Hi Dave,

	I am looking at the contents of the archive 
	"sources folder for bootstrapping(must unpack).zip"

	There are 3 log files: 

	1/- strongtalkchange.log (7,796KB 10/17/2006 1:40PM)
	2/- strongtalSave.log (1KB 10/17/2006 1;40PM)
	3/- strongtalkrestore.log (0KB 10/17/2006 1:27PM)

	1 id file "strongtalksource.id" (1KB 10/17/2006 1:40PM)

	836 .class files 
	963 no-extension files

	Most of the no-extension files have a corresponding file.

	Would you please explain the relationship between these files,
	and what does it mean when a no-extension file does not have 
	.class counterpart.

	What can one do with these files if there is available a bootstrap
	image (built from what?) and a latest and greatest VM.

	Thanks for your help.

	PhiHo

	
	P.S: What does the extension .dlt stands for?
		Is it "dynamic language type" ;-)




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---