$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Steve M. Robbins (steve_at_[hidden])
Date: 2008-04-23 21:38:44
On Wed, Apr 23, 2008 at 08:58:42AM +0400, Vladimir Prus wrote:
> On Tuesday 22 April 2008 12:02:40 Steve M. Robbins wrote:
> Is it technically possible to have two different versions of Boost package
> install
> 
> 	libfoo.so.1.35.0
> 
> and 
> 
> 	libfoo.so.1.36.0
> 
> and have some way to select either of those during compilation. Maybe, having
> 
> 	libfoo-1.35.so
> 
> and
> 
> 	libfoo-1.34.so
> 
> as symlinks? 
Sure.  That's what we have today, except that the link libraries are
named libfoo-1_34_1.so and libfoo-1_35.so.
> I'm basically looking into some way to still make upgrade
> from 1.35.0 to 1.35.1 to not require rebuilding applications
Do you mean that application A, compiled against 1.35.0, should use
1.35.1 without recompiling?  I think that's a dangerous game given
that Boost makes no claim about ABI compatibility.
> > OK.  As soon as Boost stops providing two variants based on threading,
> > we'll stop building them for Debian.  ;-)
> 
> Boost builds a single variant by default right now. 
True, and that has caused some consternation amongst the masses.
> It's Debian that forces several variants to be created ;-)
Touché!  Maybe we should build only the multithreaded variants
and see if we get any complaints ... 
Chimo,
-Steve