On Sat, Jan 23, 2016 at 6:19 PM, Chris Barker <chris.barker@noaa.gov> wrote:
1) each package that needs a third partly lib statically links it in. 2) each package that needs a third partly lib provides it, linked with a relative path (IIUC, that's how most Windows packages are done. 3) We establish some standard for providing binary libs as wheels, so that other packages can depend on them and link to them.
In my view, *all* of these are valid options. I think much of this will need to be worked out by the communities -- especially if individual packages and subcommunities decide to take the option (3) approach. I hope this PEP will enable the communities involved in OpenGIS, audio processing, image processing, etc to work out the solutions that work for them and their users. Perhaps one thing that is missing from the PEP is an explicit statement that option (3) is compatible with the manylinux1 tag -- bundling is a valid solution, but it's not the *only* solution. -Robert