Required for games-simulation/openttd-1.4.0.
Separate ebuilds for OpenGFX may have been necessary in the past, but doesn't appear so anymore. You simply go to "online content" after upgrading OpenTTD to a new version, and then select "Update installed packages" (I don't remember the exact wording). OpenGFX will then be updated in-game.
(In reply to Leif Biberg Kristensen from comment #1) > Separate ebuilds for OpenGFX may have been necessary in the past, but > doesn't appear so anymore. Forget this. You'll need a pre-packaged OpenGFX for a fresh OpenTTD install. If however you already have ottd installed, you can update the ogfx from ingame.
I believe you can start openttd with no data files whatsoever (even opengfx) and it will download them to user's directory from openttd content servers.
Indeed OpenTTD can start without any graphics set present and should then offer the user to download. Yet I'd not see that as the recommended way. However, I was notified today by an OpenTTD player that OpenTTD 1.4.1 crashed on him with both, OpenTTD 1.4.1 and OpenGFX 0.5.0 installed. While it's also a bug in OpenTTD itself, the reason of the crash is a bug in the OpenGFX package or its dependencies shipped: the file opengfx.obg had empty md5sums entries for the grf files. Building OpenGFX depends on both nml and grfcodec packages (the latter ships with grfid which calculates the md5sums over the relevant parts of the grf files as needed for the obg file)
Created attachment 378684 [details] Ebuild for games-misc/opengfx-0.5.1
Created attachment 378686 [details, diff] Patch for games-misc/opengfx-0.5.1
what's going on with this type of change? - $(_V)-rm -rf custom_tags.txt custom_tags.txt.cache + $(_V) -rm -rf custom_tags.txt custom_tags.txt.cache
Created attachment 378714 [details, diff] Patch for games-misc/opengfx-0.5.1 (In reply to Mr. Bones. from comment #7) > what's going on with this type of change? > > - $(_V)-rm -rf custom_tags.txt custom_tags.txt.cache > + $(_V) -rm -rf custom_tags.txt custom_tags.txt.cache Oh, I'm sorry, that was a leftover from before when I got errors like "bash: m: command not found". I've cleaned it up now.
in portage.