Saturday, October 03, 2020

Re: [new] games/shapezio (factorio like)

On Mon, Sep 21, 2020 at 11:17:21AM +0200, Solene Rapenne wrote:
> Please find a port for the commercial and opensource game
> https://github.com/tobspr/shapez.io/
>
> I made a desktop file running electron on the game assets, it displays
> an error about performance issue and that you should use a faster
> browser, but I didn't manage to find performance difference than in
> Chromium.
>
> Upstream doesn't seem packaging friendly. There are no documentation
> for building the game except "run yarn and yarn gulp". The whole
> upstream sources including the 1400 nodejs dependencies is more than
> 3GB and this is required to build the game files that only are 30MB
> and arch independant.
>
> I'll regularly keep the game tarball updated by building the files
> myself. The building process is insane and can't be done in ports
> (one of the fix is to link /usr/local/bin/node into /tmp/node !!!)
>
> Note that you can host the game files anywhere on a http server and
> play the game within a web browser.
>
> AFAIK, this is the first devel/electron consumer!
> Anyone ok for import?

Hm, doesn't run here. electron either segfaults when running with

/usr/local/bin/electron /usr/local/share/shapez.io/index.html

or just displays a white window with no activity. That's on -current
with a fresh download of electron from the packages. Machine is an
i7-10700 with 8G RAM, integrated Intel UHD Graphics 630.

I don't get a usable backtrace with egdb:

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000fe3c4c3f821 in ?? ()
[Current thread is 1 (process 514016)]
(gdb) bt full
#0 0x00000fe3c4c3f821 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0xfe64cec0f40

> V = 202009192141

I think following the versioning by upstream would avoid EPOCH or other
problems in the future. Latest releast was 1.1.18 from June 27th. If
you start with 202009192141, you will need EPOCH if you ever want to
switch to the upstream versioning.
In my opinion it would be best to either use the 1.1.18 release,
or if the commits between then and 2020-09-19 are desirable, maybe
version it as 1.1.18pl20200919 ?

No comments:

Post a Comment