On Tue, 2009-09-08 at 08:04 +0200, Damien Cassou wrote:
On Mon, Sep 7, 2009 at 7:51 PM, Ross Boylan<ross@biostat.ucsf.edu> wrote:
So, I think it is not looking for the sources in the image directory. Ideally, it would; alternately, the error message should be consistent with the current behavior.
Both solutions are viable solutions normally.
It may have failed to find the sources because of the oddity I mentioned in another email: though I ran from a top level directory, squeak seemed to think it was running in a subdirectory. I did not have a link to the sources in that subdirectory. Maybe some interaction with symlinks. Original setup proj/sub/x.image proj/sub/x.changes Create proj/x.image and proj/x.changes as symlinks to the corresponding files under sub. Create proj/SqueakV39.sources as a symlink to the real one. Invoke squeak from proj/ (squeak executable under proj/sub2/). The cache directory for downloading packages ended up in proj/sub/cache and save as saved to proj/sub. This suggests it may have been looking for sources in proj/sub, where they weren't, rather than proj/, where they were. Ross