Closed
Description
In turbodbc we link against pyarrow in such a fashion that turbodbc picks up the Arrow libraries via a relative RPATH in the same virtualenv. Thus we don't need to include them in the manylinux1 wheel of Turbodbc. With auditwheel's current behaviour they are sadly grafted into turbodbc's wheel. To fix this, two options come to my mind:
- whilelist all libraries that are contained in the virtualenv
- explicitly whitelist some libraries via a commandline option
I'm happy to implement one of these approaches but I would like to hear what the preferred one would be.