On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
No, but Spur has new class formats which are not recognized by SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
Levente
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
No, but Spur has new class formats which are not recognized by SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the “old” monticello is incompatible to the Class formats of SPUR, right?
On Tue, Oct 28, 2014 at 12:31 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
No, but Spur has new class formats which are not recognized by
SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the “old” monticello is incompatible to the Class formats of SPUR, right?
Arguably. But simply update Monticello to Monticello-eem.592 or later and there's no problem. Can we not do that for the SqueakSource image?
On 28.10.2014, at 22:31, Eliot Miranda eliot.miranda@gmail.com wrote:
On Tue, Oct 28, 2014 at 12:31 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
No, but Spur has new class formats which are not recognized by SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the “old” monticello is incompatible to the Class formats of SPUR, right?
Arguably. But simply update Monticello to Monticello-eem.592 or later and there's no problem. Can we not do that for the SqueakSource image?
Should be possible. But I have no access to it.
While we are at it; can we make provisions for GemStone class formats? They differ ever so slightly and it is really hard to keep all in sync.
We now have: Squeak/Pharo Class formats (ca Squeak 3.8 - Squeak 4.6/Pharo3.0) Squeak/Pharo SPUR Class Formats (current and possibly onward) GemStone class formats (somewhat mapped from the squeak ones)
I did a bit of coding for the gemstone monticello version about one or two years back and the mapping between the known monticello class formats and gemstone class formats is a little fragile, I think.
Best -Tobias
Hi Tobias,
On Tue, Oct 28, 2014 at 3:03 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 22:31, Eliot Miranda eliot.miranda@gmail.com wrote:
On Tue, Oct 28, 2014 at 12:31 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
No, but Spur has new class formats which are not recognized by
SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the “old” monticello is incompatible to the Class formats of SPUR, right?
Arguably. But simply update Monticello to Monticello-eem.592 or later
and there's no problem. Can we not do that for the SqueakSource image?
Should be possible. But I have no access to it.
While we are at it; can we make provisions for GemStone class formats? They differ ever so slightly and it is really hard to keep all in sync.
I wouldn't know, but perhaps you could take a look? I had to do very little to support a new format. The one method I needed to modify was MCClassDefinition>>#kindOfSubclass
We now have:
Squeak/Pharo Class formats (ca Squeak 3.8 - Squeak 4.6/Pharo3.0) Squeak/Pharo SPUR Class Formats (current and possibly onward)
GemStone class formats (somewhat mapped from the squeak ones)
I did a bit of coding for the gemstone monticello version about one or two years back and the mapping between the known monticello class formats and gemstone class formats is a little fragile, I think.
Best -Tobias
On Tue, Oct 28, 2014 at 03:21:15PM -0700, Eliot Miranda wrote:
Hi Tobias,
On Tue, Oct 28, 2014 at 3:03 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 22:31, Eliot Miranda eliot.miranda@gmail.com wrote:
On Tue, Oct 28, 2014 at 12:31 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible???
No, but Spur has new class formats which are not recognized by
SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the ???old??? monticello is incompatible to the Class formats of SPUR, right?
Arguably. But simply update Monticello to Monticello-eem.592 or later
and there's no problem. Can we not do that for the SqueakSource image?
Should be possible. But I have no access to it.
While we are at it; can we make provisions for GemStone class formats? They differ ever so slightly and it is really hard to keep all in sync.
I wouldn't know, but perhaps you could take a look? I had to do very little to support a new format. The one method I needed to modify was MCClassDefinition>>#kindOfSubclass
Tobias,
If you do anything with this, please let me know if I can help. Your own work on SqueakSource is more advanced than whatever we are currently running on squeak.org and squeaksource.com, but if you want or need access to those images I'll make sure you can get a copy. I don't think that we should make them publicly downloadable because they may contain passwords and personal information.
Note that I am not really a squeaksource expert, I'm just trying to keep squeaksource.com running reliably. I'll try to update Monticello in a copy of the existing squeaksource.com image, but if you have something better that includes Gemstone support I would be happy to follow your lead if possible.
Dave
On Tue, Oct 28, 2014 at 02:31:38PM -0700, Eliot Miranda wrote:
On Tue, Oct 28, 2014 at 12:31 PM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible???
No, but Spur has new class formats which are not recognized by
SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the ???old??? monticello is incompatible to the Class formats of SPUR, right?
Arguably. But simply update Monticello to Monticello-eem.592 or later and there's no problem. Can we not do that for the SqueakSource image?
Good question. We should try it and find out. The source.squeak.org and squeaksource.com servers are now running on pretty much the same image, so if we can fix it for one we will fix it for both.
I'll try to look into this soon if noone else gets to it first.
Dave
squeak-dev@lists.squeakfoundation.org
-
David T. Lewis -
Eliot Miranda -
Levente Uzonyi -
Tobias Pape