Accessing an MC repository in a postscript of a .cs ? Why ?

Bert Freudenberg bert at impara.de
Sun Jun 4 21:42:40 UTC 2006


Alexandre -

this postscript slipped into the "Unnamed1" changeset. You probably  
just renamed that, without seeing the postscript, and then filed it out.

When building the next image, it would be good to clean out the  
current changeset:

	ChangeSet current clear.
	ChangeSet current name: 'Unnamed1'.

(this code is from ReleaseBuilder>>initialCleanup)

- Bert -

Am 04.06.2006 um 15:47 schrieb stéphane ducasse:

> This is the way we generate new image from MC.
> We produce a cs that connects to the repository, fecthes the latest  
> scriptloader and execute it.
> There is no other way.
>
> Stef
>
> On 4 juin 06, at 15:20, Alexandre Bergel wrote:
>
>> Hello,
>>
>> I just filed out a changeset, and when I loaded it back, it tried  
>> to access something remotely. I inspected the file, and discovered  
>> there is the following at the end:
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> "Postscript:
>> Leave the line above, and replace the rest of this comment by a  
>> useful one.
>> Executable statements should follow this comment, and should
>> be separated by periods, with no exclamation points (!!).
>> Be sure to put any further comments in double-quotes, like this one."
>>
>> |repository|
>> repository := MCHttpRepository
>>                 location: 'http://source.squeakfoundation.org/39a'
>>                 user: ''
>>                 password: ''.
>> (repository loadVersionFromFileNamed: 'ScriptLoader-sd.173.mcz')  
>> load.
>>
>> ScriptLoader new updateFrom7025
>> !
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>
>> I do not know if having this piece of code at the end of each .cs  
>> file is a bug or a feature.
>> Is there a rational behind ?
>>
>> I used a 7032 image.
>>
>> Cheers,
>> Alexandre
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.cs.tcd.ie/Alexandre.Bergel
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>





More information about the Squeak-dev mailing list