August 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Catalog down
by Torsten Bergmann Aug. 2, 2017

Aug. 2, 2017

4 4

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process
by phil＠highoctane.be Aug. 1, 2017

Aug. 1, 2017

Massive. What is in the super small image? Is Hermes going to be a generic binary content loader? Phil On Aug 1, 2017 11:58, "Pavel Krivanek" <pavel.krivanek(a)gmail.com> wrote: Hello, we are checking a huge pull request #177 (https://github.com/pharo- project/pharo/pull/177) that will change some basics of the bootstrap process: Now we will bootstrap a smaller image that will not include compiler/parser. Compiler and related packages are exported and loaded using a binary exporter named Hermes. The compiler is then used to load FileSystem and Monticello. The rest of the bootstrap process will be the same as before. As the result we will have faster bootstrap and better system modularization and possibilities. It required some modularization efforts: - simplified initialization scripts - Use Zinc converters and encoders instead of FilePathEncoder and old TextConverter - Use Stdio instead of FileStream - Using File instead of FileSystem - Deprecated FileStream & childs (Moved to Deprecated70) - Extracted Path classes to their on package: FileSystem-Path - Moved OpalEncoders to their own package. They are required by the runtime (not only for compilation) - Introduced AsciiCharset in the kernel to answer to #isLetter #isUppercase and so on without requiring full Unicode tables from the beginning - Cleaning up a bit the full exception logging infrastructure (streams, transcript, files, stack printing...) - Split Ring methods required for system navigation to the Ring-Navigation package - Remove usages of #translated in the kernel - Refactored the bootstrapping classes to remove duplications - Cleaning up dependencies in CompiledMethod>>printOn: - fix path printing We need to merge these changes at once and of course it can cause some conflicts with the existing pull requests or external code. Anyway, we need to merge it as soon as possible. So please, try to look at the PR and test the resultant image [1] to avoid some major problems. [1] https://ci.inria.fr/pharo/view/7.0/job/70-PR-Check-Load/ lastSuccessfulBuild/artifact/bootstrap-cache/Pharo7.0-32bit-9c0691d.zip Cheers, -- Pavel

1 0

Launcher and Pharo 6.1
by Sean P. DeNigris Aug. 1, 2017

Aug. 1, 2017

Is it safe to replace the Launcher VM with the one required for Pharo 6.1? I.e. is that VM backward compatible with a Pharo 6.0 image? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-and-Pharo-6-1-tp4957770.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3