New recipe: MEOS

[evetion]

MEOS (Mobility Engine, Open Source) is a C library and its associated API for manipulating temporal and spatiotemporal data. It is the core component of MobilityDB, an open source geospatial trajectory data management & analysis platform built on top of PostgreSQL and PostGIS.

See https://libmeos.org/

edit: This release now points to the release candidate 1 release (as it requires no patches) to build. Is it ok to set the version number to v1.2.0 already and later at the actual release just rerunning it with the new commits (producing a jll with the +1 postfix)?

[evetion]

This fails on PROJ not being found, because:
┌ Warning: Dependency Proj_jll does not have a mapping for artifact Proj for platform x86_64-linux-gnu-libgfortran3-cxx03.

However, I'm not sure how/why the libgfortran(3) gets injected, and why PROJ_jll has no such mapping, whereas GEOS_jll with a similar mapping does.

edit: @giordano Could you help me out here? I'm overlooking something, but can't pinpoint it.

[imciner2]

edit: This release now points to the release candidate 1 release (as it requires no patches) to build. Is it ok to set the version number to v1.2.0 already and later at the actual release just rerunning it with the new commits (producing a jll with the +1 postfix)?

I'd suggest not doing that. The postfix is not really liked by the general registry, so while we use it for the individual builds here, it would be better to not rely on it for this.

How soon will upstream release 1.2.0?

[evetion]

edit: This release now points to the release candidate 1 release (as it requires no patches) to build. Is it ok to set the version number to v1.2.0 already and later at the actual release just rerunning it with the new commits (producing a jll with the +1 postfix)?

I'd suggest not doing that. The postfix is not really liked by the general registry, so while we use it for the individual builds here, it would be better to not rely on it for this.

How soon will upstream release 1.2.0?

Fair enough, let's wait for the 1.2.0 release, but I'm not sure how soon that will be. For now, this is also still blocked on Windows (Error: incorrect register '%eax' used with 'q' suffix), for which I made an upstream issue.

[mschoema]

We just produced the v1.2.0 release of MEOS. Feel free to let us know if you encounter any issues with it.

[fingolfin]

I am confused: why is the recipe called MEOS build it builds a project called "MobilityDB". I just went to https://github.com/MobilityDB/MobilityDB and it doesn't mention "MEOS" in the README.md (though there is a subdirectory called meos).

So is MEOS a subset of MobilityDB? But building MobilityDB for some reason... only builds and installs MEOS, not the whole thing?

Perhaps it would be good to add a few comments to explain the situation? Or rename this recipe?

[evetion]

I think that's explained in the PR description (and on the linked website). I will add a similar comment with the link to the source here.

[giordano]

I think you need compat bounds for geos (#3844) and proj (I guess there's a reason if there's a non-zero major offset at

Yggdrasil/P/PROJ/build_tarballs.jl

Line 7 in 6bd4ab3

version_offset = v"2.0.0"

)