What the system is telling you is that:
while the code of the projects is in your image/changes, the system
does not know (it cannot invent because
you could running it on the moon or mars for example) where are the git
repositories where it could find the
working copies
You have to set up your repositories through a fork. You can read:
https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo#step-1-setting-up-your-repository
That applies for all repositories: iceberg, spec2, etc.
From: da...@totallyobjects.com
Sent:
David,
Since you have so much trouble building on Windows, I would suggest building a
deployment image on macOS and then copy that over to Windows (*.image *.changes
*.sources), install a VM on Windows, and run headless with a startup.st script.
Sven
> On 11 Apr 2021, at 13:43,
> wrote:
>
Sven and everyone else, these are good, pragmatic suggestions. But, the lack of
understanding is surely frustrating for David (and for me watching from the
sidelines).
Can anyone explain why the Windows experience is so radically different from
everything else? (Ok, I admit that Windows is a ho
Hi, I use Pharo 8 & 9, 32 & 64 on Windows 10 without any problems,
except when packages use complex directory structure (path length
challenge) that was already mentioned in Seaside thread and elsewhere.
Repositories Pharo, Pharo-spec2 etc. are not needed for usual tasks,
except if you would l
That worked perfectly. I copied the three files across, created a new VM,
copied my database and (apart from a single issue) everything worked fine.
Thank you so much for your help. It never occurred to me that this would be
possible.
There is one big difference between Windows and the Mac but
