+1 (non-binding) On Mon, Jul 4, 2022 at 6:39 AM Sutou Kouhei <k...@clear-code.com> wrote:
> Hi, > > I'm developing the C API for DataFusion: > https://github.com/datafusion-contrib/datafusion-c/ > > DataFusion itself is developed by ASF but the C API isn't > developed by ASF. Because it's developed under > https://github.com/datafusion-contrib/ . > > I want to create .deb/.rpm of the C API for DataFusion like > .deb/.rpm of Apache Arrow C++/C GLib. And I want to add them > to the following our APT/Yum repositories: > > * https://apache.jfrog.io/ui/native/arrow/almalinux/ > * https://apache.jfrog.io/ui/native/arrow/amazon-linux/ > * https://apache.jfrog.io/ui/native/arrow/centos/ > * https://apache.jfrog.io/ui/native/arrow/debian/ > * https://apache.jfrog.io/ui/native/arrow/ubuntu/ > > I think that there is no problem that we mix "official" > packages (packages of Apache Arrow C++ and C GLib) and > "unofficial" packages (packages of the C API for DataFusion) > in our APT/Yum repositories. Because > https://www.apache.org/legal/release-policy.html doesn't > reject this case (doesn't mention this case) and our APT/Yum > repositories don't use > https://dist.apache.org/repos/dist/release/ . > > If there is any concern, please correct me. > > > Here are reasons why I want to add .deb/.rpm of the C API > for DataFusion to our APT/Yum repositories: > > 1. Some packages of the C API for DataFusion depend of > Apache Arrow C GLib. If both packages of the C API for > DataFusion and Apache Arrow C GLib in the same APT/Yum > repositories, users can add only one APT/Yum repository > to install the C API for DataFusion. > > 2. I want to reuse existing package release features in > apache/arrow to reduce cost to release packages. > > > FYI: We have an issue about this but there is no discussion > and no detailed description: > https://github.com/datafusion-contrib/datafusion-c/issues/8 > > > Thanks, > -- > kou >
