Skip to content

Add a one-command refresh against upstream MEOS - #11

Merged
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:tooling/one-command-refresh
Jul 28, 2026
Merged

Add a one-command refresh against upstream MEOS#11
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:tooling/one-command-refresh

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

tools/refresh-from-master.sh refreshes the generated MEOS.NET/Internal/*.cs against upstream MEOS in one command: it runs the shared MobilityDB/MEOS-API refresh-binding.sh over this repo, deriving the catalog and libmeos from MobilityDB master and regenerating via tools/codegen.py. tools/refresh.conf holds this binding's last leg: codegen.py takes the catalog path as an argument (so CATALOG_DEST is empty), then dotnet build + dotnet test against the derived libmeos. .gitignore excludes the wrapper's .meos-chain/ scratch. The wrapper and the refresh.conf shape are the same as every other MobilityDB binding.

tools/refresh-from-master.sh refreshes the generated MEOS.NET/Internal/*.cs against upstream MEOS in one command: it runs the shared MEOS-API refresh-binding.sh over this repo, deriving the catalog and libmeos from MobilityDB master and regenerating via tools/codegen.py. tools/refresh.conf holds this binding's last leg; codegen.py takes the catalog path as an argument (CATALOG_DEST empty), then dotnet build + test against the derived libmeos. .gitignore excludes the .meos-chain scratch.

Byte-identical wrapper and the same refresh.conf shape as every other MobilityDB binding.
@estebanzimanyi
estebanzimanyi merged commit 8ad54ee into MobilityDB:main Jul 28, 2026
1 check passed
@estebanzimanyi
estebanzimanyi deleted the tooling/one-command-refresh branch July 28, 2026 23:15
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