On Nov 10, 2013, at 2:05 PM, Camillo Bruni <camillobr...@gmail.com> wrote:
> It did not solve the issue yet :/, I will have to look into it next week. Don't ;) You should not touch Pharo related things and start use pomodoroes to blast your phd Stef > In any case, I think it would be unrelated to a bootstrap since FileLocator > is already lazily initialized. There is just the typical problem on how and > when to update a singleton… Ok so this is good then. > > I should reopen the issue since the problem persists. > > On 2013-11-10, at 12:37, Stéphane Ducasse <stephane.duca...@inria.fr> wrote: >> Camillo >> >> I read the bug entry and your explanation. >> Now could not we find a solution that is not based on postscript? >> Why? because I'm thinking that soon (or later) we will bootstrap from >> sources and I would love to have >> as much as behavior inside the initialize so that we do not forget a little >> message and get the system shaky. >> >> Stef >> >>>> On 09 Nov 2013, at 15:37, Johan Fabry <jfa...@dcc.uchile.cl> wrote: >>>>> For double completeness ;-) The one-click download Pharo3.0-mac.zip has >>>>> the same problem. The included source file is in the wrong directory. It >>>>> should be moved out of Contents/Resources and moved into Contents/MacOS. >>>>> Then the one-click also runs. >>>> >>>> That seems to be a regression from how it once was, so it should be fixed >>>> ASAP. >>> >>> It was fixed and actually extended to take more source locations into >>> account. >>> But somehow FileLocator is not properly initialized and thus the additional >>> locations >>> are not properly resolved. > >
