On Sun, Nov 04, 2012 at 04:14:00PM +0100, St?phane Ducasse wrote:
We looked a bit at OSProcess in 2.0 with Mariano on Friday. We tried to have clean loading (i.e., remove FileDirectory references + a couple of other stuff). We also spotted some inconsistencies in the ConfigurationOfOSProcess.
Good!
I'm going to continue what we started but I don't think I will be able to make all the tests pass (if I remember well, they are not passing in 1.4 summer neither...)
Where should I commit the changes?
if you cannot in the os repo you can in the PharoTaskForces but let us wait that david reply.
Hi, I am open to suggestions :) Doing the work in PharoTaskForces would make sense to me. I don't mind doing integration work to pull things into the OSProcess repository, as long as we do not break the tests for OSProcess running in Squeak. But I am quite familiar with the Squeak environment, so it probably makes sense for me to do the work of testing that. Overall my time is kind of limited so it is better for me of others can do the Pharo development. In the CommandShell repository, I have a package called "CommandShellPharo" for compatibility things. Maybe we should have something similar like "OSProcessPharo" for OSProcess? Note that I am suggesting "CommandShellPharo" and "OSProcessPharo" rather than "CommandShell-Pharo" and "OSProcess-Pharo" because I still maintain "CommandShell" and "OSProcess" MCZ packages the repositories, so I would like to keep any Squeak/Pharo specifics in distinct packages. If there was an OSProcessPharo (or similar) package in PharoTaskForces, I can copy the updates into the OSProcess repo, or give someone the access to do so (currently Sebastian Sastre and Damien Pollet have developer access). Dave