https://gitlab.synchro.net/main/sbbs/-/commit/2631ca69bb6a4c0929867b20
Modified Files:
src/doors/syncscumm/build.sh deploy.js xtrn/cascadequest/README.md install-xtrn.ini xtrn/spacequest0/README.md install-xtrn.ini xtrn/syncbass/.gitignore README.md install-xtrn.ini xtrn/syncqueen/.gitignore README.md install-xtrn.ini
Log Message:
syncscumm: name the door binary syncscumm, not scummvm

The build output was ScummVM's default "scummvm". This IS our build (the Synchronet backend compiled in), so name it "syncscumm": it matches the
door family and the sysop-facing syncscumm.ini config, and it avoids any
PATH collision with a system-installed "scummvm" when the xtrn.ini cmd
runs it. ScummVM's configure has no exe-name option, so build.sh renames
the binary after make (the vendored build system is left untouched);
deploy.js finds the new name; the four door cmds (scummvm%. ->
syncscumm%.), the two denylist .gitignores, and the four READMEs follow.

The per-user ScummVM config stays scummvm.ini: it genuinely is ScummVM's
own config, and syncscumm.ini is ALREADY the door's own sysop-config
filename (subtitles, sixel_max, [audio]; syncscumm.cpp reads it beside
the binary), so renaming the config to match would collide two unrelated
files in one directory. The resulting scheme is coherent -- "syncscumm"
names our things (the binary, the sysop syncscumm.ini), "scummvm.ini"
stays ScummVM's own per-user config.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net