Hi Stef, I tried to merge the changes with mcz packages that Niall prepared. As it says in the commit comment the code is broken. The difference of SUnit in Pharo is so substantial that almost every method was a conflict. I spent a few hours and tried to merge the changes manually, but in the end it did not work as expected. There are some subtle bugs in the SUnit code and some tools we have in Squeak are broken afterwards.
A better strategy would probably be to apply the changes manually as they are described on the slides of Niall. Merging the code definitely does not work. Lukas 2009/9/27 Stéphane Ducasse <[email protected]>: > lukas > > what should we do? > > SUnit-lr.76.mczFilename: SUnit-lr.76.mcz > Author: > Timestamp: 13 September 2009 1:07:41 pm > UUID: df933429-8228-4ae9-938b-3565231fd2f5 > Ancestors: SUnit-adrian_lienhard.75.mcz > Message: > > Trying to merge the SUnit 3.2 changes, but the difference of Pharo > with SUnit 3.1 seems to be so substantial that nearly half of the > complete code base conflicts with the SUnit 3.2 code. This code should > incorporate the code, but it somehow seems to be subtly broken. > Downloads: Web: 5 > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
