Hi,
Thanks to Steve, Bernd, and Josselin for ideas.
On Sat, Feb 23, 2008 at 09:17:24PM -0800, Steve Langasek wrote:
Decorate only the shared library names with the python versions, and retain
the current names for the .a files and .so symlinks - with two separate -dev
packages that conflict with one another?
That still prevents anyone from packaging an extension that builds for both
python2.4 and python2.5 at once using Boost.Python, but I think it solves
all the other drawbacks of the other solutions you suggested.
Indeed. Do you think this is a serious restriction? Given that
Debian likes to package extensions for all python versions, I tend to
think it will become a problem.