yes, it was. Probable nobody updated ConfigurationOfOSProcess as Johan is loading an old version. Try getting the last one or use #bleedingEdge On Sun, Jul 10, 2011 at 3:16 PM, Stéphane Ducasse <stephane.ducasse@inria.fr

wrote:

strnage I thought the new version of OS Process fixed that.

On Jul 10, 2011, at 3:03 PM, Johan Brichau wrote:

...

Hi guys,

I'm (finally) trying out the new Pharo1.3 Yesterday I had a couple of issues with build 13284 but 13285 seems to fix these.

Great!

But I'm now trying to load OSProcess in Pharo 1.3 and OSProcess tries to add its image startup script to the list right after ImageSegment's image startup script. However, it appears that #ImageSegment is no longer in the startup list, which yields an error.

I don't know if this is expected, so I thought I should email it here.

For now, I changed OSProcess so that it adds its startup script right after SmalltalkImage instead. I'm not sure if that is OK though... it's just a quick fix I made right now. I'm not sure what the prerequisites of OSProcess are in that respect.

Any thoughts?

Johan

-- Mariano http://marianopeck.wordpress.com

I had the opposite problem a while back: ConfigurationOfCitezen was choosing a version of Seaside for me, and #loadNoWeb was the solution. The other question I always have is which incantation to use? The situation is improving, but short of studying the code in each config each time one builds an image, I have yet to find a robust way to load things. My latest attempt (untested) appears below. Bill "7-11 - configs change over time - try to make one thing that can work." tryThese := { [config load. ]. [config project stableVersion load. ]. [config project latestVersion load. ]. }. versionStringOrNil isNil ifTrue:[ "7-11 - can this mask complexities? config load." tryThese detect:[ :each | [ each value. true. ] on:Error do:[ :e | false. ]. ]. ] ifFalse:[ ( config project version:versionStringOrNil ) load. ]. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Johan Brichau [johan@inceptive.be] Sent: Sunday, July 10, 2011 4:07 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] loading OSProcess in Pharo1.3 You are right... except that I am not using a ConfigurationOfOSProcess strange... my metacello config just points to the repository and loads the OSProcess package... why is it loading an older version? probably another config that I am loading that points to it? ... argh... thanks, at least I know now :-) On 10 Jul 2011, at 20:08, Mariano Martinez Peck wrote: yes, it was. Probable nobody updated ConfigurationOfOSProcess as Johan is loading an old version. Try getting the last one or use #bleedingEdge On Sun, Jul 10, 2011 at 3:16 PM, Stéphane Ducasse <stephane.ducasse@inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: strnage I thought the new version of OS Process fixed that. On Jul 10, 2011, at 3:03 PM, Johan Brichau wrote:

Hi guys,

I'm (finally) trying out the new Pharo1.3 Yesterday I had a couple of issues with build 13284 but 13285 seems to fix these.

Great!

But I'm now trying to load OSProcess in Pharo 1.3 and OSProcess tries to add its image startup script to the list right after ImageSegment's image startup script. However, it appears that #ImageSegment is no longer in the startup list, which yields an error.

I don't know if this is expected, so I thought I should email it here.

For now, I changed OSProcess so that it adds its startup script right after SmalltalkImage instead. I'm not sure if that is OK though... it's just a quick fix I made right now. I'm not sure what the prerequisites of OSProcess are in that respect.

Any thoughts?

Johan

-- Mariano http://marianopeck.wordpress.com<http://marianopeck.wordpress.com/>