If they are already in the repo removing them will not reduce the size, the
purpose of source control is to keep all artifacts.  Additionally I know
from experience that relying on "pip install" will not work for more than
around 1 to 2 years.  Clearly the GPL code could be an issue however only
if someone is trying to build a commercial version of Cloudberry and is not
willing to provide source code for that module.  I do not see an issue.

On Tue, Feb 25, 2025 at 10:12 AM tuhaihe (via GitHub) <g...@apache.org>
wrote:

>
> GitHub user tuhaihe created a discussion: [Ideas] Remove Bundled Python
> Packages in Cloudberry Main Repo
>
> ### Description
>
> During the code cleanup process, I noticed that the Cloudberry main repo
> includes source tarballs for several Python packages under
> `gpMgmt/bin/pythonSrc` and `gpMgmt/bin/pythonSrc/ext`, such as:
>
> ```
> * PyGreSQL-5.2.tar.gz
> * PyYAML-5.3.1.tar.gz
> * behave-1.2.6.tar.gz
> * mock-1.0.1.tar.gz
> * parse-1.8.2.tar.gz
> * psutil-5.7.0.tar.gz
> * pylint-0.21.0.tar.gz
> * setuptools-36.6.0.tar.gz
> ```
>
> While most of these packages are under Apache-compatible licenses, just
> noticed that `pylint-0.21.0.tar.gz` is licensed under GPL-2, which may
> raise license compatibility concerns.
>
> Bundling these source packages in the repo has some potential drawbacks:
>
> 1. It increases the size of the source code repository.
> 2. It introduces challenges in managing open-source license compliance,
> especially for non-Apache-compatible licenses.
>
> Would it be possible to remove these bundled source packages and instead
> install them via package managers like `pip` during the build or test
> process, or install them in our build or test docker image? This would
> simplify repo management and ensure better compliance with licensing
> policies.
>
> Maybe we need to do some source code refactoring work to adopt this
> strategy.
>
> Looking forward to hearing your thoughts!
>
> ### Use case/motivation
>
> _No response_
>
> ### Related issues
>
> _No response_
>
> ### Are you willing to submit a PR?
>
> - [ ] Yes I am willing to submit a PR!
>
> GitHub link: https://github.com/apache/cloudberry/discussions/961
>
> ----
> 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
>
>

Reply via email to