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

Re: [Pharo-dev] Moving from mc to tonel?

by Henrik Sperre Johansen

Stephan Eggermont-3 wrote > On 05-12-17 08:59, Peter UhnÃ¡k wrote: >> > In my case, it turned out to be a non-UTF8 encoded character in one >> of the commit messages. >> >> I've ran into this problem in a sister project (tonel-migration), and do >> not have a proper resolution yet. I was forcing everything to be >> unicode, so I need a better way to read and write encoded strings. :< > > To be exact, exactly none of the older commits will be UTF8 encoded. For > most it doesn't matter as they are ASCII, but if we want to have a > change of converting older french or german code (or japanese), we need > support for what was done with WideString. That probably needs a look in > the squeak mailing list archives. > > Stephan The mcz reader used to import the .bin file (which contained correctly serialized WideStrings), only falling back to reading the .st file if .bin was not present, has this changed? Or do these tools explicitly ignore the .bin file and try to read the .st file directly? If so, the MCDataStream class used to read .bin format still seems to be in the image... One could also create a tool to check/convert all mcz in a repo as a preprocess; if .bin contents decode as WideString, check that .st starts with utf8 BOM, if not, convert. Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 14, 2017

[Pharo 7.0-dev] Build #384: 20836-Cleaning-comments

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #384 was: SUCCESS. The Pull Request #595 was integrated: "20836-Cleaning-comments" Pull request url: https://github.com/pharo-project/pharo/pull/595 Issue Url: https://pharo.fogbugz.com/f/cases/20836 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2017

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Pavel Krivanek

Works for me :-) This update will simplify things a lot because as soon as you create a branch from FogBugz issue, the Iceberg does following [1]: - fetches the pharo-project repository - checkouts to the particular commit from which the image was bootstrapped - creates a new branch That means that: - you do not need to keep your fork up-to-date manually - things should be cleaner So as soon as your local repository is created as clone of your fork repository (your fork is origin), you do not need to set push and pull target nor synchronize your fork with pharo-project repository. Esteban will fix me if I'm wrong ;-) [1] see IcePharoCreateBranchFromIssue>>#createBranchNamed: -- Pavel 2017-12-14 13:19 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi! > > Iâm working on simplifying the contribution process, after collecting > opinions/experiences last couple of months. > As you know, Pharo contribution process is still WIP and we aim to have it > as smooth as possible for Pharo 7.0 release. Now, after observe the idea of > the âsystem repositoriesâ was a bad idea because it introduced extra and > non standard âpathâ to contribution, I managed to remove that to > reestablish âthe regular wayâ: you will now need to add pharo repository > just as any other repository you add, by cloning or adding local repository. > > I took Guilleâs doc and moved it to pharo project (it does not has sense > to have it living in a contributorâs repository when is so important). You > can find it here: > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > This document is also updated to reveal this new process, please read it. > > How to update your startup scripts? > Some people has added startup scripts to easy the first part of > contribution. Instead enabling system repositories, etc. you now need to > replace that with this: > > (IceRepositoryCreator new > location: '/path/to/pharo-project/pharo' asFileReference; > subdirectory: 'src'; > createRepository) > register > > PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is > very important that document reflects new process and works reliable in > different scenarios (I validated it on macOS and Windows, and assumed it > worked fine on linux but you knowâ¦ bad assumptions is the base of failure > ;) ) > > Iâm eager to hear your feedback and continue enhancing the process. > > (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) > > cheers! > Esteban >

Dec. 14, 2017

[Pharo 7.0-dev] Build #383: 20832-boostrap-process-should-use-IceProxyMCVersionInfo-instead-system-repositories

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #383 was: SUCCESS. The Pull Request #584 was integrated: "20832-boostrap-process-should-use-IceProxyMCVersionInfo-instead-system-repositories" Pull request url: https://github.com/pharo-project/pharo/pull/584 Issue Url: https://pharo.fogbugz.com/f/cases/20832 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2017

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Marcus Denker

> On 14 Dec 2017, at 13:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi! > > Iâm working on simplifying the contribution process, after collecting opinions/experiences last couple of months. > As you know, Pharo contribution process is still WIP and we aim to have it as smooth as possible for Pharo 7.0 release. Now, after observe the idea of the âsystem repositoriesâ was a bad idea because it introduced extra and non standard âpathâ to contribution, I managed to remove that to reestablish âthe regular wayâ: you will now need to add pharo repository just as any other repository you add, by cloning or adding local repository. > > I took Guilleâs doc and moved it to pharo project (it does not has sense to have it living in a contributorâs repository when is so important). You can find it here: > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> > I updated http://pharo.org/contribute-propose-fix <http://pharo.org/contribute-propose-fix> to point to this link. Marcus

Dec. 14, 2017

[Pharo 7.0-dev] Build #382: 20680-Add-comments-to-FileSystem-packages

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #382 was: SUCCESS. The Pull Request #603 was integrated: "20680-Add-comments-to-FileSystem-packages" Pull request url: https://github.com/pharo-project/pharo/pull/603 Issue Url: https://pharo.fogbugz.com/f/cases/20680 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2017

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Esteban Lorenzano

ah yesâ¦ this will be starting next build. Esteban > On 14 Dec 2017, at 13:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi! > > Iâm working on simplifying the contribution process, after collecting opinions/experiences last couple of months. > As you know, Pharo contribution process is still WIP and we aim to have it as smooth as possible for Pharo 7.0 release. Now, after observe the idea of the âsystem repositoriesâ was a bad idea because it introduced extra and non standard âpathâ to contribution, I managed to remove that to reestablish âthe regular wayâ: you will now need to add pharo repository just as any other repository you add, by cloning or adding local repository. > > I took Guilleâs doc and moved it to pharo project (it does not has sense to have it living in a contributorâs repository when is so important). You can find it here: > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> > > This document is also updated to reveal this new process, please read it. > > How to update your startup scripts? > Some people has added startup scripts to easy the first part of contribution. Instead enabling system repositories, etc. you now need to replace that with this: > > (IceRepositoryCreator new > location: '/path/to/pharo-project/pharo' asFileReference; > subdirectory: 'src'; > createRepository) > register > > PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is very important that document reflects new process and works reliable in different scenarios (I validated it on macOS and Windows, and assumed it worked fine on linux but you knowâ¦ bad assumptions is the base of failure ;) ) > > Iâm eager to hear your feedback and continue enhancing the process. > > (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) > > cheers! > Esteban

Dec. 14, 2017

[IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Esteban Lorenzano

Hi! Iâm working on simplifying the contribution process, after collecting opinions/experiences last couple of months. As you know, Pharo contribution process is still WIP and we aim to have it as smooth as possible for Pharo 7.0 release. Now, after observe the idea of the âsystem repositoriesâ was a bad idea because it introduced extra and non standard âpathâ to contribution, I managed to remove that to reestablish âthe regular wayâ: you will now need to add pharo repository just as any other repository you add, by cloning or adding local repository. I took Guilleâs doc and moved it to pharo project (it does not has sense to have it living in a contributorâs repository when is so important). You can find it here: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> This document is also updated to reveal this new process, please read it. How to update your startup scripts? Some people has added startup scripts to easy the first part of contribution. Instead enabling system repositories, etc. you now need to replace that with this: (IceRepositoryCreator new location: '/path/to/pharo-project/pharo' asFileReference; subdirectory: 'src'; createRepository) register PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is very important that document reflects new process and works reliable in different scenarios (I validated it on macOS and Windows, and assumed it worked fine on linux but you knowâ¦ bad assumptions is the base of failure ;) ) Iâm eager to hear your feedback and continue enhancing the process. (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) cheers! Esteban

Dec. 14, 2017

[Pharo 7.0-dev] Build #381: 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #381 was: SUCCESS. The Pull Request #605 was integrated: "20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference" Pull request url: https://github.com/pharo-project/pharo/pull/605 Issue Url: https://pharo.fogbugz.com/f/cases/20796 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2017

[Pharo 7.0-dev] Build #380: 20684-Categorizer-should-categorize-reset-methods-in-initialization-protocol

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #380 was: SUCCESS. The Pull Request #604 was integrated: "20684-Categorizer-should-categorize-reset-methods-in-initialization-protocol" Pull request url: https://github.com/pharo-project/pharo/pull/604 Issue Url: https://pharo.fogbugz.com/f/cases/20684 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2017