Skip to content

fix(vcpkg): bump MEOS port pin to current MobilityDB master#128

Closed
estebanzimanyi wants to merge 1 commit intomainfrom
fix/vcpkg-meos-pin-bump
Closed

fix(vcpkg): bump MEOS port pin to current MobilityDB master#128
estebanzimanyi wants to merge 1 commit intomainfrom
fix/vcpkg-meos-pin-bump

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

Summary

Bumps vcpkg_ports/meos/portfile.cmake REF from f11b7443e (Mar 30) to ee27da1a6 (current master). The newer MEOS exposes the catalog-type enum as MeosType (PascalCase) and ships the spatial-rel exports (tcontains_geo_tgeo, tdisjoint_*, tintersects_*, ttouches_*, tdwithin_*, tpoint_minus_geom) in their orthogonal 2-/3-arg form.

The MobilityDuck source already uses these names and signatures; the older pin made CI fail with 'MeosType' does not name a type and too many arguments to function 'Temporal* tcontains_geo_tgeo(...)'.

Test plan

Bumps `vcpkg_ports/meos/portfile.cmake` REF from `f11b7443e` (Mar 30)
to `ee27da1a6` (current `master`).  The newer MEOS exposes the
catalog-type enum as `MeosType` (PascalCase) and ships the spatial-rel
exports (`tcontains_geo_tgeo`, `tdisjoint_*`, `tintersects_*`,
`ttouches_*`, `tdwithin_*`, `tpoint_minus_geom`) in their orthogonal
2-/3-arg form — both required by the source on `feat/parity-additions-batch`.
@estebanzimanyi
Copy link
Copy Markdown
Member Author

Superseded by PR #126 — the port bump alone fails to compile because main lacks the drift fixes for spatial-rel exports. Folded the bump into PR #126 (commit 215cb79) so the bump and the drift fix land together. Branch fix/vcpkg-meos-pin-bump will be deleted.

@estebanzimanyi estebanzimanyi deleted the fix/vcpkg-meos-pin-bump branch May 10, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant