Hi Yanni, On 20 Feb 2013, at 22:23, Yanni Chiu <[email protected]> wrote:
> On 19/02/13 12:22 PM, Esteban Lorenzano wrote: >> >> We are almost there for the release, but we still need a little >> effort more. Would be terrific if everyone of you took the latest 2.0 >> image and test it with your usual workflows (we cannot imagine all, >> they are infinite :) > > I usually keep a build tracking the upcoming Pharo release, but when I tried > to do it during early Pharo-2.0 development, the code was not stable. Then I > never got back to it. Here's what happened, when I tried to build with the > newest version. Thanks for testing, thanks for the feedback. > First try: "Notice: Your VM is too old for this image. Please download the > latest VM." > > Get latest coglinux, from http://www.mirandabanda.org/files/Cog/VM/ > > Second try: "Can't infer base LD_LIBRARY_PATH. Aborting. Try adding a line > for /lib/i686/cmov/libc.so.6 ..." > > Patch squeak shell script with a case for "/lib/i686/cmov/libc*" > > Third try: No complaint about LD_LIBRARY_PATH, but still says "VM is too old > ..." > > Switch to a CogVM (early version of PharoVM) that was lying around. This is a bit to be expected when you use older VMs, the one-click or designated Pharo (NBCog) VMs would have prevented these issues. > More tries: > > Can't load Seaside. Update to newer seaside31.st script from > https://github.com/renggli/builder/tree/master/scripts > > Magritte3/Pier3 has deprecations and undefined class. > > Revert to trying Seaside30. Get: > *** Warning: Warning: This package depends on the following classes: > BlockContext > You must resolve these dependencies before you will be able to load these > definitions: > renderOn: > > Go back to trying Magritte3/Pier3 on Seaside31 again. Ignore the > deprecations, find: FileSystem-Legacy, at: > http://smalltalkhub.com/mc/dh83/fisleg/main > Can now load Pier3 into Pharo-20558. > > Figure out where to get the latest Zinc-Seaside. (Found at > http://www.squeaksource.com/ZincHTTPComponents). Start Seaside, go to Pier > link, get deprecation warnings about #includesSubString:. Try to disable > warnings in System Settings. Still get warnings in webpage. Change to > #includesSubString: to not call #deprecated:on:. Now, can see default Pier > page. It will be a while before all third party packages are properly ported to Pharo 2.0. Many are, but that depends mostly on their authors. Now, Seaside 3.1 and friends will load and work proper on Pharo 2.0, it is just not an out-of-the-box it-just-works experience. The #includesSub[S|s]tring: issue is easy to solve, it just requires a decision on the part of the Seaside developers. See http://forum.world.st/Broken-build-because-of-use-of-includesSubstring-tt4662939.html There also seem to be some technical reasons why a Metacello Configuration is not yet there. I guess that user pressure, once 2.0 is out, is the only thing that will make a difference. These things sometimes go slowly. This is all open source. > Next step, try to load my custom code… Let us know how it goes ! Regards, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
