GitHub user tuhaihe added a comment to the discussion: [Ideas] Remove Bundled Python Packages in Cloudberry Main Repo
Yes, I understand that not all discussions can engage more people. However, we still need to try to make the major change process open to the public. I'm glad to see your response, and I appreciate your great question. I cannot guarantee that the pip-installed packages function properly. I see that they are just tarball files, and we haven't altered them at all since they were imported. I blamed these files' commit history and found that they were imported by the PR https://github.com/apache/cloudberry/pull/16, which was used in the obsolete CI/CD workflow following the GP compile method. And more, before our Cloudberry init commits, they were referenced as a submodule from here - https://github.com/vmware-archive/pythonsrc-ext/tree/135d649aef8b70eb4ee8ec824f869026ac3f2b28 in the GP repo, then were changed in the commit https://github.com/greenplum-db/gpdb-archive/commit/2419657827ce0b3314aed29777108b0ae0414ce5 - as GP decided to change their building tool on which they were unable to fetch submodules from outside repos. In this commit, GP developers said users can also install these packages from PyPI. Given the license management for ASF compliance, I want to explore the possibility of installing them by the pip way, but it will certainly be an experiment. If you can provide more information, I would appreciate your help. Love to hear more feedback on this topic. GitHub link: https://github.com/apache/cloudberry/discussions/961#discussioncomment-12763102 ---- This is an automatically sent email for dev@cloudberry.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cloudberry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org For additional commands, e-mail: dev-h...@cloudberry.apache.org
