- Pharo-dev - lists.pharo.org

Re: [Pharo-project] nativeboost google groups

by S Krish

I too prefer one mail chain... On Tuesday, January 29, 2013, StÃ©phane Ducasse wrote: > but this is always good to know the limit of key infrastructure of pharo. > So now we will not know it, only if we register to the google group. > > Stef > > > it's mostly offtopic low-level stuff which has nothing to do with Pharo > per se. > > > > hence separate mailing list, plus it's much easier to separate > discussions ;). > > > > > > On 2013-01-28, at 23:55, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr<javascript:;>> > wrote: > >> why? > >> because this is cool to see that there is activity around NB > >> > >> Stef > >> > >>> I thought it might be a good idea to outsource the nativeboost > discussions from the main mailinglist. > >>> So I started a new google groups: > >>> > >>> https://groups.google.com/forum/?fromgroups#!forum/nativeboost > >>> nativeboost(a)googlegroups.com <javascript:;> > >>> > >>> cami > >> > >> > > > > > > >

Jan. 29, 2013

Re: [Pharo-project] TxText configuration

by Denis Kudriashov

Hello 2013/1/29 Camillo Bruni <camillobruni(a)gmail.com> > Who's in charge of the development of TxText right now? > It would like the maintainers on the ci-job description: > > https://ci.inria.fr/rmod/job/TxText/ > > > thanks :) > > Last changes is my and I continue development (slowly). But I know nothing about ci-jobs. What I can do? Also Tristan Bourgois join development. And sombody (Igor) should add him to contributors.

Jan. 29, 2013

Re: [Pharo-project] how can we create project in SmalltalkHub

by Tudor Girba

Hi, I already created the Moose team. Cheers, Doru On Jan 29, 2013, at 1:09 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I mean projects that are not under StephaneDucasse. > Should I create a Moose team to create the Moose Project? > > Stef > -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

Jan. 29, 2013

Re: [Pharo-project] pharo-project.org down?

by Sean P. DeNigris

Paul DeBruicker wrote > I can't access it. It's up now... -- View this message in context: http://forum.world.st/pharo-project-org-down-tp4666036p4666041.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 29, 2013

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

by Sean P. DeNigris

David T. Lewis wrote > I have updated CommandShell for Pharo 2.0, and made a few additional > updates to OSProcess also. In addition to CommandShell-Piping... Thanks again, David. OSProcess & Piping are absolutely essential, and CommandShell is really cool. It's so important that we have them working well :) -- View this message in context: http://forum.world.st/The-monkey-is-back-in-town-tp4658091p4666040.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 29, 2013

[Pharo-project] pharo-project.org down?

by Paul DeBruicker

I can't access it. http://downforeveryoneorjustme.com/www.pharo-project.org says its down

Jan. 29, 2013

[Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

by David T. Lewis

I have updated CommandShell for Pharo 2.0, and made a few additional updates to OSProcess also. In addition to CommandShell-Piping, the rest of the CommandShell package (except for CommandShell-MVC) can now be loaded into Pharo 2.0. CommandShellPharo provides the menu registration to make "Command shell" available under "Tools" in the world menu. The repository is at http://www.squeaksource.com/CommandShell, and the latest versions are: CommandShell-Base-dtl.29 CommandShell-Piping-dtl.13 CommandShell-Commands-dtl.13 CommandShell-UI-dtl.10 CommandShell-Morphic-dtl.2 CommandShellPharo-dtl.2 Yes I know, it needs a ConfigurationOfCommandShell. There are test failures related to VM issues but the basic functionality is now working, and both OSProcess and CommandShell should now be working for Pharo on Unix/Linux (and hopefully Mac) VMs. Dave On Thu, Jan 24, 2013 at 08:38:03PM -0500, David T. Lewis wrote: > > OSProcess and CommandShell-Piping should now load cleanly in Pharo 2.0. > > The latest versions are OSProcess-dtl.75 and CommandShell-Piping-dtl.13 > in the SqueakSource repositories for OSProcess and CommandShell. > > Thanks to Damien Cassou for doing the original work for OSProcess support > in Coral. I adapted his work so it will now load in both Squeak and Pharo. > > Unit test notes: > > The AioEventHandlerTestCase failures are due to AioPlugin not included in > the VM. I expect the tests will pass if AioPlugin is added to VM builds. > > Many test rely on #forkSqueak to create cooperating OS processes for the > tests. These tests fail on Cog, although this does not affect basic > functionality of OSProcess itself. > > UnixProcessAccessorTestCase>>testRedirectStdOutTo fails due to a problem > introduced in the oscog branch of the OSProcessPlugin. This should be fixed > in the plugin but is a minor concern and does not affect normal usage > of OSProcess. > > Dave >

Jan. 29, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by StÃ©phane Ducasse

On Jan 28, 2013, at 9:29 PM, Dale Henrichs wrote: > Metacello does use the package cache, but there _are_ certain specifications that can force a load from the repository: > > 1) If a configuration is blessed as #development, the configuration will be downloaded from the repository when referenced (to ensure that you are picking up the latest configuration > > 2) If you have a "naked" package in a specification (i.e/, no file: specified), then Metacello will _ALWAYS_ access the repository to load the LATEST mcz file...most often this is triggered when you load a baseline version (where no file: are specified). > > Moose tends to reference baselines in this manner to ensure that the latest packages are loaded. This is the most likely cause of your "problem". > > If you've specified a file: and Metacello finds the file in the package-cache it does not hit the repository to download the file. Thanks for the explanation. I'm happy because I found my bug (in fact you found my bug :). And there is a lesson. Do not code when you are too tired. Dale. > Dale > > ----- Original Message ----- > | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > | Sent: Monday, January 28, 2013 7:05:16 AM > | Subject: [Pharo-project] How to force Metacello to use the package cache? > | > | Hi guys > | > | I'm trying to work on Moose and I get 200 package to download during > | my experiments ~ 30 min at minimum > | Does anybody have an idea how to make sure metacello use the package > | cache? > | > | I started to comment > | > | cacheGofer > | > | cacheGofer == nil > | ifTrue: [ > | "don't use a caching Gofer here, since we expect the contents to > | change during a fetch operation" > | cacheGofer := Gofer new. > | >>>> cacheGofer disablePackageCache. > | cacheGofer repository: self cacheRepository. ]. > | ^ cacheGofer > | > | But no success so far. > | > | Still looking around > | Stef > | >

Jan. 29, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by Dale Henrichs

Metacello does use the package cache, but there _are_ certain specifications that can force a load from the repository: 1) If a configuration is blessed as #development, the configuration will be downloaded from the repository when referenced (to ensure that you are picking up the latest configuration 2) If you have a "naked" package in a specification (i.e/, no file: specified), then Metacello will _ALWAYS_ access the repository to load the LATEST mcz file...most often this is triggered when you load a baseline version (where no file: are specified). Moose tends to reference baselines in this manner to ensure that the latest packages are loaded. This is the most likely cause of your "problem". If you've specified a file: and Metacello finds the file in the package-cache it does not hit the repository to download the file. Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Monday, January 28, 2013 7:05:16 AM | Subject: [Pharo-project] How to force Metacello to use the package cache? | | Hi guys | | I'm trying to work on Moose and I get 200 package to download during | my experiments ~ 30 min at minimum | Does anybody have an idea how to make sure metacello use the package | cache? | | I started to comment | | cacheGofer | | cacheGofer == nil | ifTrue: [ | "don't use a caching Gofer here, since we expect the contents to | change during a fetch operation" | cacheGofer := Gofer new. | >>>> cacheGofer disablePackageCache. | cacheGofer repository: self cacheRepository. ]. | ^ cacheGofer | | But no success so far. | | Still looking around | Stef |

Jan. 29, 2013

[Pharo-project] how can we create project in SmalltalkHub

by StÃ©phane Ducasse

Hi guys I mean projects that are not under StephaneDucasse. Should I create a Moose team to create the Moose Project? Stef

Jan. 29, 2013