On 2019/02/02 10:00:37, Suvayu Ali <[email protected]> wrote: > Hello Javier,> > > On Fri, Feb 01, 2019 at 06:51:34PM -0800, Javier Luraschi wrote:> > > Hi, in order to make Arrow available to the R community through CRAN (R's> > > package archive), we need to get the Arrow binaries submitted to the Debian> > > <https://www.debian.org/doc/manuals/distribute-deb/distribute-deb.html#adding-packages-to-debian>> > > and> > > the Fedora> > > <https://fedoraproject.org/wiki/New_package_process_for_existing_contributors>> > > repositories.> > > I'm only an Arrow user, but I'm interested in packaging Arrow C++ and PyArrow> > for Fedora[1] (and RPi). As far as I understand it, there are several > hurdles> > to Fedora packaging at the moment.>
I am also trying to package Arrow C++ and PyArrow for openSUSE but have run into similar roadblocks myself. > 1. Fedora doesn't allow including external dependencies. In my experience> > building arrow on Fedora, the way external deps like Protobuf, Thrift, > RE2,> > etc are handled is unlikely to pass package review. There maybe > exceptions,> > but it has to be well justified (e.g. ROOT).> openSUSE has a similar policy, with an additional caveat: openSUSE usually doesn't allow static libraries. So even if system libraries were supported, we wouldn't be able to use them because arrow requires them to be statically linked. So supported dynamically linked libraries would be needed. > 2. As of today, I have been unable to build pyarrow on Fedora. It has to be > built> > against the distribution packages, relying on Conda will most definitely > fail> > package review.> Same here. Do you have an issue number so I can check if it is the same problem? And conda is an absolute no-go. The whole point of conda is it creates packages that are ideally largely independent of your system python install. But we want to provide packages for our system python install
