Not an answer, but what's wrong with just cloning it and checking out the relevant commit when building arrow? On Thu, Nov 2, 2017 at 10:30 AM Uwe L. Korn <uw...@xhochy.com> wrote:
> Hello, > > we would like to vendor the current stable-4.x branch of jemalloc in > Arrow C++ as we rely on the current latest commit for working with it. > As the performance benefits of jemalloc are quite large, this is a > burden, we would be ready to take. As jemalloc is a non-Apache project, > we would need to be careful of the IP. jemalloc itself is licensed under > the 2-clause BSD license. > > Would it be ok to include jemalloc sources alongside in the Arrow > tarball with LICENSE amended accordingly? Do we need to also put Apache > License headers in all of jemalloc files? Is this even possible or would > we need a code donation for the whole process? > > Uwe >
