cli/manifest/build: tt package build and fetch#1323
Open
bigbes wants to merge 1 commit into
Open
Conversation
bigbes
force-pushed
the
bigbes/tntp-8232-native-modules
branch
from
July 17, 2026 08:38
b12164e to
ee008a7
Compare
bigbes
force-pushed
the
bigbes/tntp-8611-tt-build
branch
from
July 17, 2026 08:38
17bf195 to
c9e5a72
Compare
bigbes
marked this pull request as ready for review
July 17, 2026 08:38
Orchestrate the full package build cycle, stitching the earlier waves (model, version, resolver, rocks adapter, component backends) into one pass that materializes the project's .rocks/ tree. In order: derive the version, run pre_build, gate the lock (resolve and rewrite unless --locked), materialize the pinned closure, run each component's build backend, lay component files out under their install namespace, generate version.lua, then run post_build. tt package fetch is the same materialization step in isolation: strictly from the lock, no resolve and no backends. Include/exclude uses go-git's gitignore matcher with the spec defaults (always-on hazard excludes plus the component's own patterns); .lua land under share/tarantool/<ns>/ and .so under lib/tarantool/<ns>/, flat when the namespace is empty. version.lua is generated under the package name and a component shipping one there is a collision (exit 1); a stale lock under --locked is exit 1; a component build backend failure is exit 2. Lifecycle hooks reuse the backend machinery through a new RunHook under the reduced contract (no TT_OUTPUT_DIR/TT_COMPONENT_NAME). Filtering, layout, version.lua, product selection, the lock gate and materialization are unit-tested on fixtures; the live cc/Tarantool build of my-app is gated behind the integration tag. Part of TNTP-8611
bigbes
force-pushed
the
bigbes/tntp-8611-tt-build
branch
from
July 17, 2026 13:43
c9e5a72 to
615addf
Compare
sssciel
approved these changes
Jul 20, 2026
patapenka-alexey
approved these changes
Jul 20, 2026
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
3 participants
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.
Orchestrate the full package build cycle, stitching the earlier waves (model, version, resolver, rocks adapter, component backends) into one pass that materializes the project's .rocks/ tree. In order: derive the version, run pre_build, gate the lock (resolve and rewrite unless --locked), materialize the pinned closure, run each component's build backend, lay component files out under their install namespace, generate version.lua, then run post_build. tt package fetch is the same materialization step in isolation: strictly from the lock, no resolve and no backends.
Include/exclude uses go-git's gitignore matcher with the spec defaults (always-on hazard excludes plus the component's own patterns); .lua land under share/tarantool// and .so under lib/tarantool//, flat when the namespace is empty. version.lua is generated under the package name and a component shipping one there is a collision (exit 1); a stale lock under --locked is exit 1; a component build backend failure is exit 2. Lifecycle hooks reuse the backend machinery through a new RunHook under the reduced contract (no TT_OUTPUT_DIR/TT_COMPONENT_NAME).
Filtering, layout, version.lua, product selection, the lock gate and materialization are unit-tested on fixtures; the live cc/Tarantool build of my-app is gated behind the integration tag.
Part of TNTP-8611