<div dir="ltr">Is there a location to pull from that would keep my image up to date with the ReleaseSqueakTrunk version of Squeak? Or if I update my image, will parts start dissappearing?<div><br></div><div>Is the only way to continue to use the ReleaseSqueakTrunk to download occasional snapshots and move all the code into it?</div>
<div><br></div><div>Or is the trunk system still working off of the release version, but the SqueakTrunk job strips out the unloadable packages as part of its job? and then the ReleaseSqueakTrunk loads them back in?</div>
<div><br></div><div>I guess I could figure this our myself, but just in case anyone else is wondering, I'll ask.</div><div><br></div><div>-Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 30, 2013 at 7:13 AM, H. Hirzel <span dir="ltr"><<a href="mailto:hannes.hirzel@gmail.com" target="_blank">hannes.hirzel@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you Frank for the explanation, I consider it to be a useful metaphor.<br>
<br>
"rehydrated" image vs. "dehydrated" image<br>
<br>
--Hannes<br>
<div class="im"><br>
On 7/28/13, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
> It's a term I picked up from work: SqueakTrunk is like a dessicated,<br>
> dried out thing that's quite small, like a dessicated pea. But<br>
> ReleaseSqueakTrunk is like the rehydrated pea, useful for cooking.<br>
<br>
</div>"rehydrated" = ReleaseSqueakTrunk<br>
<a href="http://build.squeak.org/job/ReleaseSqueakTrunk/" target="_blank">http://build.squeak.org/job/ReleaseSqueakTrunk/</a><br>
<div class="im"><br>
<br>
> As the package layering work proceeds, and more packages become<br>
> unloadable, I unload them from SqueakTrunk.<br>
<br>
</div>"dehydrated" = SqueakTrunk<br>
<a href="http://build.squeak.org/job/SqueakTrunk/" target="_blank">http://build.squeak.org/job/SqueakTrunk/</a><br>
<div class="HOEnZb"><div class="h5"><br>
> ReleaseSqueakTrunk takes<br>
> that small SqueakTrunk artifact and reloads all those unloadable<br>
> packages.<br>
<br>
<br>
<br>
> The idea is that people just keep on using the ReleaseSqueakTrunk<br>
> image, and without even realising it, are using a _constructed_ image,<br>
> built up from some small core.<br>
><br>
> frank<br>
><br>
> On 28 July 2013 18:58, H. Hirzel <<a href="mailto:hannes.hirzel@gmail.com">hannes.hirzel@gmail.com</a>> wrote:<br>
>> Question of clarification:<br>
>><br>
>> What do you mean by a 'rehydrated image'?<br>
>><br>
>> --HH<br>
>><br>
>> On 7/28/13, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>>> On Sun, Jul 28, 2013 at 08:26:18AM +0100, Frank Shearar wrote:<br>
>>>> On 28 July 2013 07:24, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>>>> > I noticed that the VM tarball jobs on <a href="http://build.squeak.org" target="_blank">build.squeak.org</a> (InterpreterVM<br>
>>>> > and<br>
>>>> > CogVM jobs) have been failing for some time. These jobs use the<br>
>>>> > latest<br>
>>>> > trunk<br>
>>>> > image from the SqueakTrunk job, which is supposed to be a base Squeak<br>
>>>> > image<br>
>>>> > updated from the trunk stream (see<br>
>>>> > <a href="http://build.squeak.org/job/SqueakTrunk/" target="_blank">http://build.squeak.org/job/SqueakTrunk/</a>).<br>
>>>> > However, that image is missing the ST80 package entirely (which<br>
>>>> > indirectly<br>
>>>> > causes the VM tarball job failures).<br>
>>>> ><br>
>>>> > I tried to update the image (world menu -> help... -> update code<br>
>>>> > from<br>
>>>> > server) in hopes that this would load the missing packages, but this<br>
>>>> > fails<br>
>>>> > due to some other problem.<br>
>>>> ><br>
>>>> > The project comment for the SqueakTrunk job says:<br>
>>>> ><br>
>>>> > * Take a base image (currently 4.5-12565), update it, archive the<br>
>>>> > result.<br>
>>>> > * Run the entire suite of in-image tests.<br>
>>>> ><br>
>>>> > I think that I had mistakenly assumed that the "SqueakTrunk" job was<br>
>>>> > a<br>
>>>> > release<br>
>>>> > image updated from the trunk stream, but actually it must be a<br>
>>>> > stripped<br>
>>>> > "base"<br>
>>>> > image with packages reloaded, and maybe the reloading part has<br>
>>>> > forgotten<br>
>>>> > to<br>
>>>> > install ST80. Is that right?<br>
>>>><br>
>>>> Yes. ReleaseSqueakTrunk contains a rehydrated/full fat Squeak image<br>
>>>> _with_ ST80 and friends loaded.<br>
>>>><br>
>>>> Sorry! I should have noticed the failing builds and connected that<br>
>>>> with the recent stripping of ST80.<br>
>>>><br>
>>><br>
>>> Not at all, it was not obvious that this was connected to the problem.<br>
>>><br>
>>> I guess that once the package reorganizing settles down, it would be<br>
>>> good to have some kind of sanity-check test to ensure that a rehydrated<br>
>>> image contains the expected set of packages.<br>
>>><br>
>>> Dave<br>
>>><br>
>>><br>
>>><br>
>><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>