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:
>
Considering easiest and cheapest, there's always self hosting, or are you
discounting that idea?
Most geeks have a bit of spare hardware laying around and broadband
up-speeds aren't too bad.
I'm guessing that if we are in the $5 a month ball park then we aren't
needing a guaranteed up time.
-
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:
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
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
