[squeak-dev] [CI] Unloading a package programmatically?

Frank Shearar frank.shearar at gmail.com
Fri Sep 9 11:18:00 UTC 2011


2011/9/9 Levente Uzonyi <leves at elte.hu>:
> On Fri, 9 Sep 2011, Frank Shearar wrote:
>
>> On 9 September 2011 04:58, Casey Ransberger <casey.obrien.r at gmail.com>
>> wrote:
>>>
>>> In the after.st script, I see this. This is probably where the build is
>>> hanging presently.
>>> "Unload Build Tools"
>>> [ Gofer new
>>>         package: 'HudsonBuildTools';
>>>         unload ]
>>>                 on: Error
>>>                 do: [ :err | "package not present" ].
>>> !
>>> This is to rid the build tools from the produced artifact, a nice touch.
>>> Since we don't have Gofer in Squeak, is there an easy way to do this?
>>
>> It shouldn't be very hard to get Gofer working in Squeak, I would
>> think. It doesn't touch the UI (or it shouldn't!) which is one can of
>> worms that needn't be opened.
>
> I guess Gofer works in Squeak (1 failure and 1 error for Gofer-Core-lr.128).
> The question is: how do you unload Gofer itself?

Why do you need to?
* Take a trunk image
* Install Gofer using Installer
* Install whatever else you want to test
* Run the tests
* Throw away the image (or, just don't save it)

> Installer can unload mc stuff, but it's broken at the moment:
>
> Installer mc unload: 'HudsonBuildTools'.
>
> There's a DNU: #freeSomeSpace, which is easy to fix, and there's
> #fixObsoleteReferences, which is too simple to work as expected.

I've recorded this on Mantis: http://bugs.squeak.org/view.php?id=7669

I've also rudely assigned it to you :)

frank

> Levente
>
>>
>> (We don't need to repeat the discussion around Installer/Gofer/Goofy:
>> I just want to see useful Pharo stuff available so we can avoid the
>> dreaded NIH syndrome. If it's ugly/overengineered/aesthetic-offending
>> and it WORKS, then I'm happy.)
>>
>> frank
>>
>
>
>
>



More information about the Squeak-dev mailing list