RE: proposal for how to synchronize Strongtalk source

"SmallSqueak" <[email protected]> Mon, 14 May 2007 03:48:36 -0400
Newsgroups gmane.comp.lang.smalltalk.strongtalk
Message-ID <[email protected]>
 
David Griswold wrote (May 13, 2007 8:49 AM):

> 
> > -----Original Message-----
> > From:  SmallSqueak
> > > -----Original Message-----
> > > From:  Ted Neward
> > > Sent: Thursday, May 10, 2007 3:49 PM
> > > To: [email protected]
> > > Subject: RE: proposal for how to synchronize Strongtalk source
> > >
> > >
> > > Go to strongtalk.org for the downloads, I think.
> > >
> >
> > 	Thanks for the pointer.
> >
> > 	I went there but the latest release available is 2.0,
> > 	with dated VM and image (Oct 01 and Sep 25, 2006 respectively).
> >
> > 	Few days back, Dave said that he updated the image
> > 	on SVN when he made a release. So it is expected that
> > 	the latest release should be a couple days old.
> 
> No, that wasn't a release, just a commit.  

David Griswold had also written (Monday, May 07, 2007 5:33 PM)


> 
> This raises a niggling problem that I have not had time to 
> address.  The strongtalk.bst image file in the repository is 
> only updated right now when I do an actual release, since I 
> do not believe we have enough room in the repository to keep 
> it up to date at each commit, because it is a large binary 
> file that probably diffs very poorly and Google's repository 
> only gives us 100MB total, which would run out very rapidly 
> if we check in a 2MB binary file every time we make any 
> Smalltalk change.  So if you don't incrementally file in all 
> the changes that I have checked in over time since the last 
> release, it will not be correct.  For now I have checked in 
> the current .bst, but then there is the associated problem 
> that the associated Smalltalk source database is not in the 
> repository, so the image will not have the right source code 
> associated with it, and almost certainly won't recompile (in 
> Smalltalk) correctly.
> 
> Of course the real answer to this is to keep only the truly 
> original, non-redundant sources in the repository and rebuild 
> the image completely whenever code is released, but that 
> requires a full bootstrap which we can't do yet.
> 
> This is a big pain in the butt, but the only solution at the 
> moment is for me to package up all these big files in some 
> kind of release that gives everyone the updated image and 
> Smalltalk source DB at the same time.  I'll try to do that 
> tomorrow, but I can't do that for every little change, 
> though, so we need a better solution, which as far as I can 
> tell will be to finish getting the system to re-bootstrap.  
> Hopefully that is coming Real Soon Now, since that is needed 
> as part of a Squeak port anyway.
> 
> I'll think about better ways of dealing with this in the interim.
> 
> Sorry for the inconvenience,
> Dave
> 


	So apparently "The strongtalk.bst image file in the repository 
	is only updated right now when I do an actual release,..."

	actually meant "The strongtalk.bst image file in the repository 
	is only updated right now when I do an actual commit,..."

David Griswold wrote:

> PhiHo isn't after the image, he is after the release, 
> because he needs the Strongtalk source db/changelog.
> Strongtalk.org is the right place for the release he needs.
> 

David Griswold also had written (May 09, 2007 11:51 AM:	

> 
> It sounds to me like you haven't actually downloaded and 
> installed the current Strongtalk release.  You can't 
> construct a working system just from the repository right 
> now, you need to start from the binary release, which will 
> set up your source directory etc first.  The repository is 
> only used for building the VM executable right now.  The 
> image and source directory etc must come from the release.
> 

	"Recompile world..." from Strongtalk 2.0 launcher with 
	either VM bundled with Strongtalk 2.0 or newly built VM 
	(revision 95) resulted in random errors at different places
	for different runs.

	Could anyone succesfully recompile Strongtalk 2.0?

> -Dave
> 

	Thanks,

	PhiHo


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---