luoyuxia commented on PR #376: URL: https://github.com/apache/fluss-rust/pull/376#issuecomment-3977058482
> > @zhaohaidao Thanks for the pr. Left minor comments. one more question, do you think we need to publish fluss-cpp to bazel registry? > > Given the current scope, where Arrow is the main external dependency, it may be more practical to keep the source-based build path as the primary approach for now, and consider Bazel registry-first adoption once dependency complexity grows. > > Bazel is most valuable when: > > * Consumers are already Bazel-native (monorepo integration via bazel_dep(...)). > * Cross-language reproducibility (Rust/C++) is a hard requirement. > * Remote cache / remote execution is available to offset heavy native builds. > * Dependency/platform complexity grows and centralized graph management is needed. > > Bazel also adds clear maintenance overhead for us: > > * Release + registry publishing workflow (versioning, tagging, submission, validation). > * Stronger backward-compatibility commitments for module/extension interfaces. > * Expanded CI matrix (Linux/macOS, build/system, registry consumption path). > * More user documentation and support obligations. > * Ongoing version lifecycle work (patch releases, backports, rollback handling). > > Recommendation now: > > * Keep source checkout + build as the default. > * Keep Bazel support available but not as the primary distribution path. > * Revisit registry-first Bazel adoption once external dependencies increase and user-side dependency conflicts become frequent. > @luoyuxia Thanks for the explanation. 👍 -- 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]
