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 horrible p.o.s. But, it's not some non-human language that cannot be understood. (Ok. Maybe it is.)) On April 11, 2021 11:56:08 PM PDT, Sven Van Caekenberghe <sven@stfx.eu> wrote:
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, <david@totallyobjects.com> <david@totallyobjects.com> wrote:
Hi everyone.
I have a simple talk, or so I thought. I am trying to port a Mac Pharo/Seaside project to either a Windows 2012 server or to a Windows 10 laptop. I have set up my git credentials and that all works fine. However, when I install either 8.0 or 9.0 on my Windows 10 laptop it shows he following Repositories -- status Pharo Local repository missing Pharo-spec2 Local repository missing Pharo-newtools Local repository missing Iceberg Local repository missing Libgit-pharo-bindings Local repository missing tonel Local repository missing
What on earth is going on here as installing Pharo on my Mac was seamless. I have to get the project onto a Windows machine as these are the only servers that I have. I really canât be this difficult, can it?
How do I get out of this mess, given that that is a clean install? David Totally Objects