On Wed, May 18, 2016 at 10:49 PM Frank Shearar <frank.shearar at gmail.com>
wrote:

> On 18 May 2016 at 13:46, Frank Shearar <frank.shearar at gmail.com> wrote:
>
>> On 17 May 2016 at 01:03, Fabio Niephaus <lists at fniephaus.com> wrote:
>>
>>> Hi all,
>>>
>>> I'm trying to understand how we build a new Squeak trunk image.
>>> AFAIK, a Jenkins projects [1] runs squeak-ci [2] to build a new image,
>>> but I'm not sure I have
>>> figured everything out that happens during the build process.
>>> I guess squeak-ci opens an older Squeak image, updates it using
>>> the MCMcmUpdater and then
>>> saves the new version. Or is there anything else that I am missing?
>>>
>>> That is the essential part of the process. The devil's in the details.
>> If you look at
>> https://github.com/squeak-smalltalk/squeak-ci/blob/master/update-image.st
>> you'll see the script squeak-ci uses to update the image. Most of that file
>> is nonsense like doing sensible things when you're offline, or handling the
>> vagaries of changed protocols in MCMcmUpdater and various other things. And
>> dumping out enormous amounts of debugging information.
>>
>
> I should add that you _should_ need to just run "rake update_base_image"
> to have the process generate a fresh image. If that doesn't work, and you
> have followed the instructions on the README, please feel free to yell at
> the maintainers through a bug report.
>
> frank
>
>
>> frank
>>
>>
>>> Best,
>>> Fabio
>>>
>>> [1] http://build.squeak.org/job/Trunk/
>>> [2] https://github.com/squeak-smalltalk/squeak-ci
>>>
>>>
>>>
>>>
>>>
>>
Thanks for the pointers. I think I understand the process now!

Fabio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20160518/717905db/attachment.htm