- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] OSProcess for Pharo 7

by Sean P. DeNigris

Max Leske wrote >> I was talking about OSSubProcess > Well, I'm not working with that at the moment ;) [OT] Just want to bump the problem that OSProcess and OSSubProcess can't currently be used in the same image. This is an important problem because users can't control which library dependencies use. Mariano hinted at a solution. It didn't seem like a ton of work, but it's beyond my understanding. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 15, 2019

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

by Sean P. DeNigris

Dale Henrichs-3 wrote > `MetacelloProjectRegistration registry` I'd like to add a clue to MetacelloProjectRegistry that one typically accesses it from MetacelloProjectRegistration, maybe in the class comment. Should I do a PR for MetaC, Pharo, or both (not quite clear on exactly how we're handling that relationship ATM)? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 15, 2019

[Pharo 7.0] Build #154: Fix comment on OSWindow >> startTextInput

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

There is a new Pharo build available! The status of the build #154 was: FAILURE. The Pull Request #2781 was integrated: "Fix comment on OSWindow >> startTextInput" Pull request url: https://github.com/pharo-project/pharo/pull/2781 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 15, 2019

[Pharo 8.0] Build #141: 2834-testExternalMorphicDependencies-failing-on-CI

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

There is a new Pharo build available! The status of the build #141 was: FAILURE. The Pull Request #2835 was integrated: "2834-testExternalMorphicDependencies-failing-on-CI" Pull request url: https://github.com/pharo-project/pharo/pull/2835 Issue Url: https://pharo.fogbugz.com/f/cases/2834 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 15, 2019

[Pharo 8.0] Build #140: 2829-RPackagepackageManifestOrNil-should-be-directly-in-RPackage-Core

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

There is a new Pharo build available! The status of the build #140 was: SUCCESS. The Pull Request #2830 was integrated: "2829-RPackagepackageManifestOrNil-should-be-directly-in-RPackage-Core" Pull request url: https://github.com/pharo-project/pharo/pull/2830 Issue Url: https://pharo.fogbugz.com/f/cases/2829 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 15, 2019

[Pharo 8.0] Build #139: 2826-remove-ReDeadMethod-and-Test

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

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

March 15, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Max Leske

On 14 Mar 2019, at 20:00, ducasse wrote: > I was talking about OSSubProcess Well, I'm not working with that at the moment ;) > >> On 14 Mar 2019, at 18:21, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Iâve been using OSProcess on OSX for exercism (development mode) >> and its been working fine. (Iâve been piping a go executable output >> to run a generation command) >> >>> On 14 Mar 2019, at 16:38, ducasse <stepharo(a)netcourrier.com> wrote: >>> >>> >>> >>>> On 14 Mar 2019, at 17:33, Max Leske <maxleske(a)gmail.com> wrote: >>>> >>>> On 13 Mar 2019, at 11:55, ducasse wrote: >>>> >>>>> Ok now one of these days we will have to have all the important >>>>> libraries hosted in the same place. >>>>> It is not sure that we will maintain MC forever. >>>>> For example SmalltalkHub should get readonly by the end of the >>>>> year (for lack of maintenance reason). >>>>> BTW is OSSubProcess working for you? >>>> >>>> Yes, it works. There appear to be some methods that need to be >>>> updated but general functionality is there. >>> >>> Let us know because Guille did a pass on Marianoâs version and we >>> are ready to improve it. >>> >>>> >>>> Max >>>> >>>>> >>>>>> Hi Stef, >>>>>> >>>>>> On 11 Mar 2019, at 8:12, ducasse wrote: >>>>>> >>>>>>> Max >>>>>>> >>>>>>> ifNotNilDo: was probably deprecated in Pharo 50 so this is a bit >>>>>>> normal that it got removed in P7. But we should check this. >>>>>>> I do not have the time today for this. >>>>>>> >>>>>>> normally ifNotNilDo: should be covered by a migrator automatic >>>>>>> rewrite rules (can you check?): Ducasse/Migrator >>>>>>> because in such case you load the migrator packages and execute >>>>>>> the tests of the OSProcess (if any) >>>>>>> then you execute OSProcess and the user of ifNotNilDo: will be >>>>>>> automatically rewritten and you are just left to check >>>>>>> the senders that are left and commit a new version. >>>>>> >>>>>> You have extensions defined for #ifNotNilDo: in your migration >>>>>> definition for 50 to 60. >>>>>> >>>>>>> >>>>>>> If IfNotNilDo: is not covered by a automated migration we should >>>>>>> add one. >>>>>>> It was deprecated before the automated migrations were >>>>>>> introduced. >>>>>>> >>>>>>> >>>>>>> Now about your question: yes a new version of OSProcess should >>>>>>> be produced for P7. >>>>>>> The best would be to migrate it to github. >>>>>> >>>>>> I think Dave might disagree ;) If the maintainers are fine with >>>>>> moving to Github then that would be great. I assume that there >>>>>> will be some objections to that (e.g. because of loading in >>>>>> Squeak?) and we (I at least) don't want to maintain a fork / >>>>>> mirror on Github. >>>>>> Pulling from SqueakSource works fine for now. >>>>>> >>>>>> Max >>>>>> >>>>>>> >>>>>>> Let me know if it helps. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>>> On 11 Mar 2019, at 08:00, Max Leske <maxleske(a)gmail.com> wrote: >>>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess >>>>>>>> loading fails. I volunteer to update OSProcess for Pharo 7 but >>>>>>>> I need someone to tell me what the expected workflow is. >>>>>>>> AFAICT, we've simply copied the current ConfigurationOf to the >>>>>>>> MetaRepoForXX in the past without making any changes specific >>>>>>>> to Pharo. That will not work this time. >>>>>>>> So, should I create a new version of OSProcess for all >>>>>>>> platforms, where #ifNotNilDo: has been replaced with >>>>>>>> #ifNotNil:? Or should I add a compatibility package for Pharo? >>>>>>>> Or something else? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Max >>>>>>>> >>>>>> >>>> >>> >>> >>> >> >>

March 14, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Tim Mackinnon

Ohh - yeah, I canât use that as it doesnât support windows right? (Itâs all a bit confusing) Tim Sent from my iPhone Sent from my iPhone > On 14 Mar 2019, at 19:00, ducasse <stepharo(a)netcourrier.com> wrote: > > I was talking about OSSubProcess

March 14, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by ducasse

I was talking about OSSubProcess > On 14 Mar 2019, at 18:21, Tim Mackinnon <tim(a)testit.works> wrote: > > Iâve been using OSProcess on OSX for exercism (development mode) and its been working fine. (Iâve been piping a go executable output to run a generation command) > >> On 14 Mar 2019, at 16:38, ducasse <stepharo(a)netcourrier.com> wrote: >> >> >> >>> On 14 Mar 2019, at 17:33, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> On 13 Mar 2019, at 11:55, ducasse wrote: >>> >>>> Ok now one of these days we will have to have all the important libraries hosted in the same place. >>>> It is not sure that we will maintain MC forever. >>>> For example SmalltalkHub should get readonly by the end of the year (for lack of maintenance reason). >>>> BTW is OSSubProcess working for you? >>> >>> Yes, it works. There appear to be some methods that need to be updated but general functionality is there. >> >> Let us know because Guille did a pass on Marianoâs version and we are ready to improve it. >> >>> >>> Max >>> >>>> >>>>> Hi Stef, >>>>> >>>>> On 11 Mar 2019, at 8:12, ducasse wrote: >>>>> >>>>>> Max >>>>>> >>>>>> ifNotNilDo: was probably deprecated in Pharo 50 so this is a bit normal that it got removed in P7. But we should check this. >>>>>> I do not have the time today for this. >>>>>> >>>>>> normally ifNotNilDo: should be covered by a migrator automatic rewrite rules (can you check?): Ducasse/Migrator >>>>>> because in such case you load the migrator packages and execute the tests of the OSProcess (if any) >>>>>> then you execute OSProcess and the user of ifNotNilDo: will be automatically rewritten and you are just left to check >>>>>> the senders that are left and commit a new version. >>>>> >>>>> You have extensions defined for #ifNotNilDo: in your migration definition for 50 to 60. >>>>> >>>>>> >>>>>> If IfNotNilDo: is not covered by a automated migration we should add one. >>>>>> It was deprecated before the automated migrations were introduced. >>>>>> >>>>>> >>>>>> Now about your question: yes a new version of OSProcess should be produced for P7. >>>>>> The best would be to migrate it to github. >>>>> >>>>> I think Dave might disagree ;) If the maintainers are fine with moving to Github then that would be great. I assume that there will be some objections to that (e.g. because of loading in Squeak?) and we (I at least) don't want to maintain a fork / mirror on Github. >>>>> Pulling from SqueakSource works fine for now. >>>>> >>>>> Max >>>>> >>>>>> >>>>>> Let me know if it helps. >>>>>> >>>>>> Stef >>>>>> >>>>>>> On 11 Mar 2019, at 08:00, Max Leske <maxleske(a)gmail.com> wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading fails. I volunteer to update OSProcess for Pharo 7 but I need someone to tell me what the expected workflow is. AFAICT, we've simply copied the current ConfigurationOf to the MetaRepoForXX in the past without making any changes specific to Pharo. That will not work this time. >>>>>>> So, should I create a new version of OSProcess for all platforms, where #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add a compatibility package for Pharo? Or something else? >>>>>>> >>>>>>> Cheers, >>>>>>> Max >>>>>>> >>>>> >>> >> >> >> > >

March 14, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Tim Mackinnon

Iâve been using OSProcess on OSX for exercism (development mode) and its been working fine. (Iâve been piping a go executable output to run a generation command) > On 14 Mar 2019, at 16:38, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 14 Mar 2019, at 17:33, Max Leske <maxleske(a)gmail.com> wrote: >> >> On 13 Mar 2019, at 11:55, ducasse wrote: >> >>> Ok now one of these days we will have to have all the important libraries hosted in the same place. >>> It is not sure that we will maintain MC forever. >>> For example SmalltalkHub should get readonly by the end of the year (for lack of maintenance reason). >>> BTW is OSSubProcess working for you? >> >> Yes, it works. There appear to be some methods that need to be updated but general functionality is there. > > Let us know because Guille did a pass on Marianoâs version and we are ready to improve it. > >> >> Max >> >>> >>>> Hi Stef, >>>> >>>> On 11 Mar 2019, at 8:12, ducasse wrote: >>>> >>>>> Max >>>>> >>>>> ifNotNilDo: was probably deprecated in Pharo 50 so this is a bit normal that it got removed in P7. But we should check this. >>>>> I do not have the time today for this. >>>>> >>>>> normally ifNotNilDo: should be covered by a migrator automatic rewrite rules (can you check?): Ducasse/Migrator >>>>> because in such case you load the migrator packages and execute the tests of the OSProcess (if any) >>>>> then you execute OSProcess and the user of ifNotNilDo: will be automatically rewritten and you are just left to check >>>>> the senders that are left and commit a new version. >>>> >>>> You have extensions defined for #ifNotNilDo: in your migration definition for 50 to 60. >>>> >>>>> >>>>> If IfNotNilDo: is not covered by a automated migration we should add one. >>>>> It was deprecated before the automated migrations were introduced. >>>>> >>>>> >>>>> Now about your question: yes a new version of OSProcess should be produced for P7. >>>>> The best would be to migrate it to github. >>>> >>>> I think Dave might disagree ;) If the maintainers are fine with moving to Github then that would be great. I assume that there will be some objections to that (e.g. because of loading in Squeak?) and we (I at least) don't want to maintain a fork / mirror on Github. >>>> Pulling from SqueakSource works fine for now. >>>> >>>> Max >>>> >>>>> >>>>> Let me know if it helps. >>>>> >>>>> Stef >>>>> >>>>>> On 11 Mar 2019, at 08:00, Max Leske <maxleske(a)gmail.com> wrote: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading fails. I volunteer to update OSProcess for Pharo 7 but I need someone to tell me what the expected workflow is. AFAICT, we've simply copied the current ConfigurationOf to the MetaRepoForXX in the past without making any changes specific to Pharo. That will not work this time. >>>>>> So, should I create a new version of OSProcess for all platforms, where #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add a compatibility package for Pharo? Or something else? >>>>>> >>>>>> Cheers, >>>>>> Max >>>>>> >>>> >> > > >

March 14, 2019