Collapsing the .spur branch for Squeak 5

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Collapsing the .spur branch for Squeak 5

Chris Muller-4
Hi Eliot, thanks for uploading the new trunk46-spur images 20150807.

However, it has four merged dirty packages.  I have already created a
Squeak5.0-15102 and uploaded it to http://ftp.squeak.org/5.0alpha/.
So, we have something which essentially reflects the last state of the
last 4.x (e.g., 4.6) in the new Spur format.  Nice.

Now we're ready to figure out how to move forward.  I think we should
save these dirty merged packages one last time as ".spur" before we
resave all of the .spur packages for the first time as the mainline
names (e.g., without ".spur").  Would you like to take care of that or
me?

Reply | Threaded
Open this post in threaded view
|

Re: Collapsing the .spur branch for Squeak 5

Levente Uzonyi-2
There's one more thing. The spur bootstrap removes ObjectHistory, but it
leaves references to the class in #oopAge and #oopTimestamp. Those methods
should also be removed, otherwise ObjectHistory will be in Undeclared in
5.0.

Levente

On Thu, 9 Jul 2015, Chris Muller wrote:

> Hi Eliot, thanks for uploading the new trunk46-spur images 20150807.
>
> However, it has four merged dirty packages.  I have already created a
> Squeak5.0-15102 and uploaded it to http://ftp.squeak.org/5.0alpha/.
> So, we have something which essentially reflects the last state of the
> last 4.x (e.g., 4.6) in the new Spur format.  Nice.
>
> Now we're ready to figure out how to move forward.  I think we should
> save these dirty merged packages one last time as ".spur" before we
> resave all of the .spur packages for the first time as the mainline
> names (e.g., without ".spur").  Would you like to take care of that or
> me?
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Collapsing the .spur branch for Squeak 5

Eliot Miranda-2
In reply to this post by Chris Muller-4
Hi Chris,

Eliot (phone)

On Jul 9, 2015, at 1:08 PM, Chris Muller <[hidden email]> wrote:

> Hi Eliot, thanks for uploading the new trunk46-spur images 20150807.
>
> However, it has four merged dirty packages.  I have already created a
> Squeak5.0-15102 and uploaded it to http://ftp.squeak.org/5.0alpha/.
> So, we have something which essentially reflects the last state of the
> last 4.x (e.g., 4.6) in the new Spur format.  Nice.
>
> Now we're ready to figure out how to move forward.  I think we should
> save these dirty merged packages one last time as ".spur" before we
> resave all of the .spur packages for the first time as the mainline
> names (e.g., without ".spur").  Would you like to take care of that or
> me?

The packages are dirty only as a left-over from the merge in the update process.  If I check for differences the dirty mark will disappear.  I had forgotten to do that.  Thanks for the reminder.  I'll do it tomorrow at the latest (booked this evening and have been busy in the day).
Reply | Threaded
Open this post in threaded view
|

Re: Collapsing the .spur branch for Squeak 5

Eliot Miranda-2
In reply to this post by Levente Uzonyi-2
Hi Levente,

    I had hoped that those two methods were deleted by the bootstrap.  Again that might be as a result of the merge.  I'll take care if it when I clean the packages.

Eliot (phone)

On Jul 9, 2015, at 2:18 PM, Levente Uzonyi <[hidden email]> wrote:

> There's one more thing. The spur bootstrap removes ObjectHistory, but it leaves references to the class in #oopAge and #oopTimestamp. Those methods should also be removed, otherwise ObjectHistory will be in Undeclared in 5.0.
>
> Levente
>
> On Thu, 9 Jul 2015, Chris Muller wrote:
>
>> Hi Eliot, thanks for uploading the new trunk46-spur images 20150807.
>>
>> However, it has four merged dirty packages.  I have already created a
>> Squeak5.0-15102 and uploaded it to http://ftp.squeak.org/5.0alpha/.
>> So, we have something which essentially reflects the last state of the
>> last 4.x (e.g., 4.6) in the new Spur format.  Nice.
>>
>> Now we're ready to figure out how to move forward.  I think we should
>> save these dirty merged packages one last time as ".spur" before we
>> resave all of the .spur packages for the first time as the mainline
>> names (e.g., without ".spur").  Would you like to take care of that or
>> me?
>>
>>