Document producing the catalog by hand#68
Merged
estebanzimanyi merged 1 commit intoJul 22, 2026
Conversation
The catalog is the root of the ecosystem chain, but the document gives its local form only as a single run.py line under Pinning, with no prerequisites and no statement of what the two possible header sources produce. Give the commands: install the Python requirements, build and install libmeos for a self-contained parse, and run run.py with MDB_SRC_ROOT pointing at the source checkout that carries the @InGroup and @sqlfn maps. State what the installed headers give that the source tree cannot, since FFI bindings depend on exact struct layouts. The ecosystem script invokes each binding's tools/regen-from-pin.sh and reports and skips a binding that has none, which is the case for JMEOS: it regenerates through tools/regen-from-catalog.sh. Say so, and point at the direct invocation.
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.
Gives the catalog — the root of the ecosystem chain — a runnable local form.
The document covers the CI path through
provision-meoswell, but its local form is a singlerun.pyline under Pinning, with no prerequisites and no statement of what the two possible header sources produce. It now carries the commands: install the Python requirements, build and install libmeos into a private prefix for a self-contained parse, and runrun.pywithMDB_SRC_ROOTpointing at the source checkout that supplies the@ingroupand@sqlfnmaps.It also states what the installed headers give that the source tree cannot. The install step writes the generated
meos_export.hwithpostgres_ext_defs.in.hspliced in place of#include <postgres.h>, so libclang resolves every struct field to its real C type and byte offset; the source tree wraps those types in stubs and yields approximate layouts. FFI bindings depend on the exact layout, so the distinction decides which invocation is correct for them.tools/ecosystem-generate.shinvokes each binding'stools/regen-from-pin.shand reports and skips a binding that has none (line 46). JMEOS regenerates throughtools/regen-from-catalog.sh, so the script skips the FFI substrate the JVM tier binds. The section now says so and points at the direct invocation.