Index | Thread | Search

From:
Thomas Frohwein <tfrohwein@fastmail.com>
Subject:
Re: [new] games/simutrans
To:
James Russell Stickney <jrs@outband.net>
Cc:
ports@openbsd.org
Date:
Wed, 17 Jan 2024 20:11:14 -0500

Download raw body.

Thread
  • Thomas Frohwein:

    [new] games/simutrans

On Wed, Mar 15, 2023 at 01:05:51AM -0400, Thomas Frohwein wrote:

[...]

I would like to follow-up about this port. It seems that the upcoming
version 123.0.2 has some changes that make this much easier to manage
as a port: The paksets (content packages) that needed to be relative to
the executable can now be stored in ~/simutrans/paksets/. There is also
a new pak installer that helps with downloading paksets when none are
present. This means that the port doesn't need the subdirectories
base/, pak/, and pak128/ anymore. There are other more existing paksets
that can be installed just as easily as the standard ones.

Since I haven't seen follow-up on this in a while - James, are you
still planning to be maintainer for this port? I left your maintainer
address in and it would be great if you could give this new version a
look and still consider maintaining it, as I'm not sure that I will
have the long-term bandwidth to follow-up on this regularly.

The attached package is now for simutrans-123.0.2alpha0 because the
game menu advertises itself as 123.0.2 already and the alpha suffix
allows for the most options in between this and the next release.
This tarball also contains fixes to find fluidsynth soundfonts from
generaluser-gs-soundfont, scummvm, or gzdoom if installed.

The fluidsynth support will only be built with the newer fluidsynth
port; the current one (1.1) is too old - see my email [1]. I've also
included comments in the Makefile to help with updating the port from
GitHub checkouts, and how to switch back to Sourceforge releases when
the time is right.

I updated the README to reflect the new reality of managing paksets. I
left out the translations for now as they currently require pulling in
online files that seem to change the ports contents and aren't just
added in.

I'm working with upstream on getting the patches added, especially for
the dr_mkdir before dr_chdir and the recursive dr_mkdir

ok to import (with/after fluidsynth update)? and with James still as
maintainer?

[1] https://marc.info/?l=openbsd-ports&m=170551090219393&w=2