Re: [pkg-boost-devel] Boost.Python: Build and Install with Python 2.4 and 2.5?

2008-02-27 Thread Steve Langasek
On Tue, Feb 26, 2008 at 10:04:26PM -0600, Steve M. Robbins wrote: 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

Re: [boost] [pkg-boost-devel] Boost.Python: Build and Install with Python 2.4 and 2.5?

2008-02-27 Thread Domenico Andreoli
Hi, On Tue, Feb 26, 2008 at 10:04:26PM -0600, Steve M. Robbins wrote: On Mon, Feb 25, 2008 at 01:15:31PM +0100, Josselin Mouette wrote: The solution is to keep the names decorated with both python versions, but to maintain a farm of symbolic links pointing to the current python

Re: [pkg-boost-devel] Boost.Python: Build and Install with Python 2.4 and 2.5?

2008-02-27 Thread Josselin Mouette
Le mardi 26 février 2008 à 22:04 -0600, Steve M. Robbins a écrit : The idea is to create a single -dev package that contains the following in /usr/lib: libboost_python-py24-gcc42-1_34_1.so libboost_python-py24-gcc42-1_34_1.a libboost_python-py25-gcc42-1_34_1.so

Re: [pkg-boost-devel] [boost] Boost.Python: Build and Install with Python 2.4 and 2.5?

2008-02-27 Thread Steve M. Robbins
On Wed, Feb 27, 2008 at 08:43:43AM -0500, Stefan Seefeld wrote: (I still don't see the problem: Source packages don't depend on binary packages, only binary packages do. Source packages *do*, in fact, depend on binary packages. Each source package describes exactly the packages required to