Version mismatch for msys2 package

[durkisneer1]

I'm using MingW64 (MSYS2) on Windows. When installing the tmxlite package, version 1.4.4, my meson project cannot detect tmxlite with a version: '>=1.4.4' flag. Upon further inspection, the tmxlite.pc file states that the package is actually version 1.3.1.

[fallahn]

From where are you installing this? I don't have any control over third party package managers, you'll have to contact the maintainer and ask them to make changes.

It looks like it's pulling in the version number from the CMakeLists.txt which was recently updated, so you may have better luck with the head revision rather than the latest release.

[durkisneer1]

I see, that was exactly the problem then. Even switching from MSYS2 to CMake's FetchContent produced the same result, so for now I'll just use "master" in my FetchContent declaration rather than "v1.4.4".

That said, it would be helpful to either fix the release itself (with a reupload or new release using CMake minimum 3.10) to preserve stable versioning, or at least clarify this in the wiki. This isn't limited to MSYS2 and FetchContent; Vcpkg users will run into the same issue, since the release still reports the fragile CMake minimum of 3.1 and the misleading tmxlite version number, even if the release source technically correspond to v1.4.4.

[fallahn]

Hm I see where you're coming from (all this is way above my pay-grade, I started this project just to load some maps into my game and it's since escalated somewhat 😅)

Is it possible to edit an existing release, or will I have to go through every file and bump the version number to create a new tag against? 🤔

[durkisneer1]

Looks like the automatic source files aren't possible to edit 😔 . I can make a PR that updates the few lines of code that would make a next release correct and modify some meson/cmake minimum versions for modern compat.

[fallahn]

If you're willing to do that, that would be fantastic, thank you!