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 <[email protected] > 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
