On 2012-12-05, at 10:05, Goubier Thierry <[email protected]> wrote:
> Le 05/12/2012 13:47, Esteban Lorenzano a écrit : >> >> On Dec 5, 2012, at 1:21 PM, Camillo Bruni <[email protected]> wrote: >> >>> >>> Sources are in my smalltalkhub repository: >>> http://smalltalkhub.com/#!/~dh83/ci >>> >>> On 2012-12-05, at 06:28, Goubier Thierry <[email protected]> wrote: >>>> Le 05/12/2012 04:43, Camillo Bruni a écrit : >>>>> I had a sudden urge to program something so I revived the monkey (partly) >>>>> >>>>> - full smalltalk implementation (no more ruby) >>>>> - basic command line handler (could be better but works..) >>>> >>>>> - using OSProcess with FileSystem-Legacy in 2.0 >>>> >>>> So that would be the way to have OSProcess in 2.0? >> >> "for now" :) >> OSProcess should load fine and without legacy when 2.0 is released > > +1. > > But I'm longing for the ability to integrate Pharo images in a mixed language > git repository by loading in there a Makefile which: > > Builds a Pharo-based tool: > - downloads the latest Pharo image and vm > - loads the additional configurations and packages as setup (filetree, for > example:)) on the command line... > - loads the local packages > - save the built image. > - install a startup shell in a bin/ or build/ directory, the image in a > share/ or lib/ somewhere. > > I know I can do that in 2.0, but I need OSProcess... then I think you should be fine with the approach I took. I think once 2.0 is declared stable someone will take care of OSProcess. So looks like 2.0 almost covered all your needs, the only thing missing is the startup shell. Of course we can extend Pharo's command line tools a bit, they are still in early stage and need improvement.. > By the way, is this expected that the current directory in a Pharo image is > not where the vm was started, but where the image file is kept? I have to use > > (PipeableOSProcess command: 'pwd') output asFileReference > > to get the true working directory. yeah, the whole working directory stuff is a mess: - FileSystem has it's own notion of working directory, - so does the rest of the Image, - the only one getting it more or less right is OSProcess :/ I wanted to unify it at some point, but well, too many things at the same time :P
