Generalize the refresh hub from JVM consumers to any binding - #79
Merged
estebanzimanyi merged 1 commit intoJul 28, 2026
Merged
Conversation
refresh-jvm-chain.sh refreshed only the JVM consumers. Every binding shares the same chain: MobilityDB -> provision-meos.sh (catalog, and for native/FFI bindings libmeos) -> the binding's own generate + build. refresh-binding.sh is that generic entry point, a superset of the JVM hub: BUILD_LIBMEOS (native vs pure-catalog), a conf-settable MDB_REF (bindings that pin a MEOS ref), a configurable CATALOG_DEST (generators that take the catalog path as an argument set it empty), and the JMEOS-jar leg made conditional on JMEOS_COORDS. refresh-jvm-chain.sh becomes a thin alias for it, so the JVM consumers keep working unchanged; a JVM consumer is just a binding whose refresh.conf sets JMEOS_COORDS.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tools/refresh-binding.shis the generic one-command refresh entry point for every binding (GoMEOS, meos-rs, PyMEOS, MEOS.NET, and the JVM consumers): MobilityDB -> provision-meos.sh (catalog, and for native/FFI bindings libmeos) -> the binding's own generate + build. It is a superset of the JVM hub:BUILD_LIBMEOS(native vs pure-catalog), a conf-settableMDB_REF(bindings that pin a MEOS ref), a configurableCATALOG_DEST(generators that take the catalog path as an argument set it empty, e.g. MEOS.NET), and the JMEOS-jar leg made conditional onJMEOS_COORDS.refresh-jvm-chain.shbecomes a thin alias for it (--consumeraliases--binding), so the three merged JVM consumers keep working unchanged. Each binding carries atools/refresh.confand atools/refresh-from-master.shwrapper. Proof: a local run over GoMEOS through this hub derives libmeos + the catalog and drives GoMEOS's own tools/codegen.py — 3129 idiomatic Go wrappers emitted from the staged catalog.