Hello, I have an application that tries to dlopen() libpython2.6.so. In accordance with the Debian Policy, section 8.4, this file is included in python2.6-dev rather than python2.6. However, running an ordinary application should probably not require a -dev package.
Can someone explain to me the reason behind this policy? What's wrong with shipping libpython2.6 so in python2.6 / why should an application dlopen() libpython2.6.so.1 rather than libpython2.6.so? I would like to convince the developers to change the dlopen() call, but I feel that I need a slightly better argument than "You probably shouldn't be doing this, because according to the Debian policy the .so link belongs in the -dev package only". Thanks, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
