On 1/7/06, Phillip J. Eby email@example.com wrote:
At 06:20 AM 1/6/2006 +0100, Matthias Urlichs wrote:
Besides, Unix systems these days tend to have the required libraries installed anyway.
Not libPyICU, since it's a part of PyICU. Similar issues may apply to other multi-extension projects that need to share a large chunk of code.
Whether this is the right way to do things is up for debate. Earlier in the thread libpng.so was thrown out as example--this immediately threw some red flags up because it's a common/standard lib that comes with most distros.
If you need .so that's built and exported by the same packaged egg, you may just consider installing it in a more benign area such as /usr/local/lib. Though, the *BSD folks may also have some thoughts on the matter. Messing with LD_LIBRARY_PATH is never the right way to go about solving this. Unless you're Oracle...
Please keep in mind that the different *nixes will want to stick with their own package formats, managers, and automatic dep solvers. Enhancing setuptools to facilitate these (bdist_rpm/bdist_deb), will be more beneficial in the long run.