zjw1111 opened a new pull request, #570: URL: https://github.com/apache/paimon-cpp/pull/570
### Purpose Linked issue: close #569 A dependency version or patch change can currently reuse sources and installed libraries marked successful by an older build. Introduce shared validation of source versions, archive checksums, ordered patches, and registered build inputs. Reject changed or incomplete state with explicit cleanup paths; preserve incremental builds when inputs are unchanged and never delete files automatically. Migrate Arrow, ORC, Jieba, OSS SDK v2, and Vortex to the shared mechanism. Align ORC and Vortex build directories with the other dependencies and remove `PAIMON_VORTEX_SOURCE_DIR`. ### Tests Add `thirdparty_patch_test.py` lifecycle coverage and invoke it from the CMake module test suite for Unix Makefiles and Ninja. The tests cover patch content changes with preserved timestamps; patch additions, removal, and ordering; source and build input changes; partial patch failures and process interruption; build/install retry; inconsistent completion records; legacy artifacts and cleanup paths; source damage and direct-step/install guards; directory migration; and unchanged-build reuse. Additional cases cover file additions/deletions, unsafe patch paths, subproject registration, cleanup followed by a clean rebuild, and the Vortex adapter's Cargo working directory and output layout using simulated Cargo. Installation checks validate completion state rather than individual installed files. ### API and Format No public C++ API, storage format, or protocol changes. Local Vortex source overrides are removed; patched dependencies use checksum-verified source archives and single-configuration CMake generators. Existing dependency builds may require the cleanup reported by the new checks. ### Documentation Update the build guide with dependency reuse, cleanup, and retry instructions. ### Generative AI tooling Generated-by: OpenAI Codex (codex-cli 0.167.0) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
