From: Thomas Frohwein Subject: Re: update for games/openomf To: Brian Callahan Cc: ports@openbsd.org, namn@messagemode2.com Date: Tue, 23 Sep 2025 07:10:13 -0400 On Thu, 18 Sep 2025 00:20:32 +0000 Brian Callahan wrote: > On 09/17/2025 04:42 PM, Thomas Frohwein wrote: > > Hi, > > > > Looks like we fell behind for a while on this port. I prepared the > > attached diff that updates it to the release 0.8.4. Among the > > changes[1] are rollback netcode since 0.8.0 which is the state of > > the art for fighting games played over internet, as far as I know > > about the topic. There is also experimental netplay spectator mode > > since 0.8.2. > > > > Portswise, I switched this to github via DIST_TUPLE for ease of > > updates rather than rolling tarballs to self-host. > > > > Of note, the SHA256 hash in the README doesn't match the freeware > > file (anymore). I haven't touched this, but maybe pointing to the > > upstream wiki[2] to follow their instructions would be more durable? > > > > ok to update? > > > > [1] https://github.com/omf2097/openomf/releases > > [2] https://www.omf2097.com/wiki/doku.php?id=download > > Yes ok; it's good to get rid of another one of my manually rolled > DISTFILES finally. > > I'm thinking you're probably right about pointing to the wiki. Manual > logging of the SHA256 hash of the freeware file is probably more > brittle than it's worth, seeing as it's subject to change at any time > without any automated flagging of said change. I've drafted an updated README in the attached diff. Besides linking to the download section of the wiki, I also updated the instructions for using a custom path to the game files. The previous way of just launching the binary from it doesn't work anymore. I looked at upstream instructions [1] and src/resources/pathmanager.c and tried the options. The only viable one for game files is setting OPENOMF_RESOURCE_DIR. The other ones (XDG_* variables, SDL_GetPrefPath fallback) don't work for those files. The directory now needs to contain both openomf.bk and ENGLISH.DAT2 from the port. ok? [1] https://github.com/omf2097/openomf/blob/master/PATHS.md Index: Makefile =================================================================== RCS file: /cvs/ports/games/openomf/Makefile,v diff -u -p -r1.9 Makefile --- Makefile 18 Sep 2025 13:29:28 -0000 1.9 +++ Makefile 23 Sep 2025 10:56:19 -0000 @@ -3,6 +3,7 @@ COMMENT = free remake of One Must Fall 2 V = 0.8.4 PKGNAME = openomf-${V} DIST_TUPLE += github omf2097 openomf ${V} . +REVISION = 0 CATEGORIES = games x11 Index: pkg/README =================================================================== RCS file: /cvs/ports/games/openomf/pkg/README,v diff -u -p -r1.3 README --- pkg/README 11 Mar 2022 19:04:46 -0000 1.3 +++ pkg/README 23 Sep 2025 10:56:19 -0000 @@ -9,18 +9,18 @@ order to work properly. While OpenOMF is Fall 2097 is proprietary and must be obtained in order to use OpenOMF. Fortunately, the developers of One Must Fall 2097 released the game as -freeware in 1999. It is available for download at archive.org: -https://archive.org/download/OneMustFall2097/OMF21cd-playable.ZIP -The above zip file has the following checksum: -SHA256 (OMF21cd-playable.ZIP) = pZ4Ke4NMfyNANwwGXkiuSjsnWzdw91uNGl3YrYi5inQ= +freeware in 1999. Please see the instructions on omf2097 wiki for how +to obtain the files: -Note that this .ZIP file will extract its contents into the working -directory! +https://www.omf2097.com/wiki/doku.php?id=download For a global installation, the game files must be placed in ${TRUEPREFIX}/share/openomf. -Alternatively, the game can be launched from any directory that holds -the game assets. If you choose this route, the file -${TRUEPREFIX}/share/openomf/openomf.bf must be copied to this -directory before launching the game. +Alternatively, the path to the game files can be specified like this: + +$ OPENOMF_RESOURCE_DIR=/path/to/files/ openomf + +If you choose this route, the files +${TRUEPREFIX}/share/openomf/{openomf.bk,ENGLISH.DAT2} must be copied to +this directory before launching the game.