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

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

by Stephane Ducasse

Hi Pavel This is super excellent! IMPRESSIVE. An image without the compiler and a reloadable compiler. Super cool. Stef On Tue, Aug 1, 2017 at 11:57 AM, 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… > > Cheers, > -- Pavel >

Aug. 1, 2017

[IMPORTANT] Following changes in the bootstrapping process

by Pavel Krivanek

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… Cheers, -- Pavel

Aug. 1, 2017

Re: [Pharo-dev] Catalog down

by Torsten Bergmann

Thanks! Â Gesendet:Â Dienstag, 01. August 2017 um 10:48 Uhr Von:Â "Christophe Demarey" <christophe.demarey(a)inria.fr> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] Catalog down It is nows back on line! Â Christophe Â Le 1 aoÃ»t 2017 Ã 08:40, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> a Ã©crit :Â It is still down. Am 31.07.2017, 19:55, Esteban Lorenzano <estebanlm@gmail.com[mailto:estebanlm@gmail.com]> schrieb:It will be restarted at midnight > On 31 Jul 2017, at 19:51, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> wrote: > > http://catalog.pharo.org/catalog/json[http://catalog.pharo.org/catalog/json] responds with "Service Temporarily Unavailable". > Sabine already reported it this morning on Discord. > > Any idea? > > Â

Aug. 1, 2017

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Pavel Krivanek

2017-07-31 22:51 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > I wasnât clear on which image to retry - the https://ci.inria.fr/pharo/ > job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccessfulBuild/ > artifact/Pharo-minimal-64.zip one still shows as being last updated 7 > days ago. > > The https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01- > ConfigurationOfMinimalPharo/ one gives me a mismatch error: This > interpreter (vers. 68021) cannot read image file (vers. 6521). > > The https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit-Conversion/ > lastSuccessfulBuild/artifact/latest-minimal-64.zip one gives me a > walkback when trying to run my install script : > > 25 UndefinedObject(Object)>>*doesNotUnderstand: #addTo:* > 26 MCRepositoryGroup>>addRepository: > 27 createRepository > | repo | > repo := self project createRepository: self. > ^ MCRepositoryGroup default repositories > detect: [ :each | each = repo ] > ifNone: [ > MCRepositoryGroup default addRepository: repo. > repo ] in MetacelloRepositorySpec>>createRepository > > I think this is because the image doesnât support Metacello? As in: > > Metacello new > repository: 'filetree://../src'; > baseline: 'Lambda'; > load. > > > How do you guys load things into the minimal images (I thought you used > Metacello - but maybe you do it some other way?) > > I can use a big 6.1 image fine (as it has Metacello loaded) but Iâd really > like a minimal solution - that can load in libraries like AWS S3, or XML > parsing etc. and it seems like I should be a good customer for kicking the > tires on all of this. > > Tim > > I checked the 64-bit Pharo 7 minimal image and loading of baseline (of SUnit from pharo-project/pharo) works: ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval --save "Metacello new baseline: 'SUnit'; repository: 'filetree://./pharo-core/src'; load." ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval "TestCase suite run" Can you test it too? -- Pavel

Aug. 1, 2017

Re: [Pharo-dev] Catalog down

by Christophe Demarey

It is nows back on line! Christophe > Le 1 aoÃ»t 2017 Ã 08:40, Torsten Bergmann <astares(a)gmx.de> a Ã©crit : > > It is still down. > Am 31.07.2017, 19:55, Esteban Lorenzano <estebanlm(a)gmail.com> schrieb: > It will be restarted at midnight > > > On 31 Jul 2017, at 19:51, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> responds with "Service Temporarily Unavailable". > > Sabine already reported it this morning on Discord. > > > > Any idea? > > > > >

Aug. 1, 2017

Re: [Pharo-dev] Catalog down

by Torsten Bergmann

Aug. 1, 2017

Re: [Pharo-dev] Launcher and Pharo 6.1

by Sean P. DeNigris

EstebanLM wrote > it is safe. 6.1 Great. Thanks, guys. I downloaded a new vm via `curl get.pharo.org/vm61 | bash` and it seems to be working fine with 6.0 images. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-and-Pharo-6-1-tp4957770p4958036.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 1, 2017