Hi Edgar,
I hope this my response meets you after a refreshing nap :)
On Mon, 14 May 2007 11:27:33 +0200, you wrote:
El 5/12/07 12:27 PM, "Klaus D. Witzel" escribió:
Yes, just did it again with a fresh Squeak3.9-final-7067.image : no
problem.
Could you send an error report?
Cheers
Klaus
What I do:
Take a fresh Squeak3.9-final-7067.image
Load in order both .cs - No problem.
For not mess the update stream , I use my
http://www.squeaksource.com/Ladrillos
The .mcz for this , using our procedure was
Collections-edc.71.mcz
Multilingual-edc.24.mcz
Since both .cs must be loaded in order, putting them into the same .mcz
will not work, instead the Unicode part of the system will be blown up
when the single .mcz is merged/loaded.
The first .cs has methods which allow the running system to change Unicode
table without crashing itself but *also* supports the (massive) change in
the Unicode table.
WOW these methods support both the old and the new Unicode table
simultaneously.
The second .cs has the "final" version of the same methods which no longer
know about the old Unicode table.
That's all about it, nothing more (and nothing less ;-)
I quit the image without save.
When I try to load Multilingual-edc.24.mcz, the image go limbo (Forever
to load), no debugger, no crash, no log.
This would also happen if both .cs files where filedIn one after the other
and then filed out into a singe .cs file (which is then filedIn alone).
This, BTW, was the reason for my to produce two distinct .cs files.
Same what in 3.10 at the time what I try the first time, and what I send
notice warning about old change sets could do things what Monticello no.
But all prefer Monticello ....
I'm not an expert in this particular realm of Monticello, all I can do
with it are the highest-level functions (like load, merge, ...).
Q: is there a way of doing:
1] file in the first .cs
2] produce the first .mcz
3] file in the second .cs
4] produce the second .mcz in such a way that it also merges the first
.mcz?
This would definitely allow to get rid of both .cs files in favour of
Monticello.
All: hey, in-situ schema transformation is rare (because everybody tries
to avoid it) but not always avoidable. How can that be done with
Monticello?
BTW: Just making a release with the first .cs and a later (perhaps minor)
release with the second .cs would fit the bill (with the exception of
performance and image size).
Cheers
Klaus
Edgar
_______________________________________________
V3dot10 mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/v3dot10
