MMm, so is the source/changes then UTF8?  If so then let me assume any UTF8 character encoding issues were addressed in the changes/sources logic as found in Pharo last year, otherwise a condense will/might trash your sources, assuming anyone notices... 


On 2010-03-29, at 1:59 PM, Andreas Raab wrote:

> Hi -
> 
> I just wanted to float an idea that Eliot came up with over lunch. He pointed out that it would be good if we could preserve the method history from 4.0 but that it also would be good if we could ship with an empty changes file. Both of which can be achieved if we'd be condensing the changes file *to the end of* the sources file, i.e,
> 
> 	SqueakV41.source = SqueakV4.sources + Squeak4.1.changes
> 
> This has some advantages besides the empty changes file. It allows us to keep up with the intermediate stages during the RCs. In other words, for the next RC I can make a SqueakV41.sources and the image will be "compatible" with later versions of the sources file. In fact, SqueakV41.sources would be compatible with with SqueakV40.sources, too, so you could link the old sources file to the new one to save space if desired.
> 
> What do people think? Sounds like a plan?
> 
> Cheers,
>  - Andreas
> 

--
===========================================================================
John M. McIntosh <johnmci at smalltalkconsulting.com>   Twitter:  squeaker68882
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
===========================================================================




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2445 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20100329/9467f170/smime.bin