[V3dot10] [Q] About updates, take 3

[Edgar J. De Cleene]

El 1/25/07 3:26 PM, "Eliot Miranda" <eliot.miranda at gmail.com> escribió:

> in the form of a long script, evasluated in a workspace.
Could be done that way
 
> ReleaseBuilder can unload itself as one of the last steps before creating the
> release image then keep it as a class/tool, otherwise just maintain it as a
> script in a well-known place, so that otehrs can use it to create their own
> images. 

Also could be done, create a Monticello and put in squeaksource for later
reuse.
And rip of image with ScriptBuilder

> (Again IMAO) One thing I think must change asap is the non-empty changes file
> that comes with a new release.  ReleaseBuilder or whatever must generate a
> fresh sources file with a null changes file.  That makes the changes file mch
> more effective for crash recovery.  It belongs to the programmer not to the
> release builder, so the release shouldn't pollute it.

At this point , is what I always wish to do.

+1



	

	
		
__________________________________________________ 
Preguntá. Respondé. Descubrí. 
Todo lo que querías saber, y lo que ni imaginabas, 
está en Yahoo! Respuestas (Beta). 
¡Probalo ya! 
http://www.yahoo.com.ar/respuestas