[pkg-boost-devel] Bug#517203: Bug#517203: raising severity, cloning for other boost packages

Steve M. Robbins steve at sumost.ca
Mon Mar 23 19:57:49 UTC 2009


On Mon, Mar 23, 2009 at 08:47:59AM +0100, Matthias Klose wrote:
> Steve, thanks for the reply.
> 
> Steve M. Robbins schrieb:
> > Matthias,
> > 
> > We have a bit of a chicken and egg problem, here.  
> > 
> > We're using the rtupdate script to create undecorated symlinks for
> > boost python libraries built against the default python.  Until Python
> > 2.6 is available to build the Boost.Python package, no such libraries
> > exist.
> > 
> > The current behaviour for the rtupdate script is to exit with an
> > error.  Is the error what is driving this bug?
> 
> yes, it breaks installation of a python (>= 2.6) package during the python 2.6
> postinst.
> 
> > I can modify the script to simply remove the existing symlinks and not
> > create any but exit with success.  Would that address the bug
> > in your eyes?
> 
> why not just extend your version check for any python version. Is there a reason
> why it is versioned at all? I couldn't find a rationale for the current behaviour.

The script is used to create undecorated symlinks to libraries built
with the "default" python version.  Right now the package builds
libraries for Python 2.4 and Python 2.5.  I don't have libraries for
any other python version.  One way I can handle "any python version"
is to simply not provide symlinks if Boost.Python doesn't have
libararies for the default version of python doesn't have.

Once Python 2.6 is in sid, I'll update boost to build libraries for
it.

-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-boost-devel/attachments/20090323/658d3a64/attachment.pgp 


More information about the pkg-boost-devel mailing list