Re: update games/fheroes2 to 0.9.18

On Mon, Sep 05, 2022 at 06:40:42PM +0200, Paco Esteban wrote:
> On Sat, 27 Aug 2022, Paco Esteban wrote:
>
> > Hi ports@,
> >
> > This is an update of games/fheroes2 to its latest version 0.9.18
> > It builds and runs fine for me on amd64, not sure I did the right thing
> > with the right thing with the lang Makefile. They seem to have changed
> > things a bit in this area.
> >
> > Maintainer on cc.
> >
> > Comments ? Ok to commit ?
>
> ping ?
>
> diff here again for convenience

Thanks Paco! I went ahead and committed the update with some changes:

- Set PATCHORIG (otherwise, some .orig files in the distfiles get
picked up).
- Install helper script 'extract_homm2_resources.sh'. This makes
installation much simpler, esp. for videos ('ANIM') of the GOG.com
distribution.
- README adjusted to reflect the simpler install of game data.

See below about the change in translations.

Otherwise, I tested this again with a fresh install from the GOG.com
files and everything works as expected.

> --- games/fheroes2/pkg/PLIST
> +++ games/fheroes2/pkg/PLIST
> @@ -2,22 +2,20 @@
> share/doc/pkg-readmes/${PKGSTEM}
> share/fheroes2/
> share/fheroes2/download_demo_version.sh
> -share/fheroes2/fheroes2.key
> share/fheroes2/files/
> share/fheroes2/files/data/
> share/fheroes2/files/data/resurrection.h2d
> share/fheroes2/files/lang/
> +share/fheroes2/files/lang/be.mo
> +share/fheroes2/files/lang/bg.mo
> share/fheroes2/files/lang/cs.mo
> share/fheroes2/files/lang/de.mo
> share/fheroes2/files/lang/es.mo
> -share/fheroes2/files/lang/fr.mo
> -share/fheroes2/files/lang/hu.mo
> share/fheroes2/files/lang/it.mo
> -share/fheroes2/files/lang/lt.mo
> share/fheroes2/files/lang/nb.mo
> -share/fheroes2/files/lang/nl.mo
> share/fheroes2/files/lang/pl.mo
> share/fheroes2/files/lang/pt.mo
> +share/fheroes2/files/lang/ro.mo
> share/fheroes2/files/lang/ru.mo
> share/fheroes2/files/lang/sv.mo
> -share/fheroes2/files/lang/tr.mo
> +share/fheroes2/files/lang/uk.mo

A few languages have disappeared - fr, hu, nl, tr. This looks like an
upstream issue as we aren't doing anything manually in the port patches
anymore. Will keep an eye out.