[kde-freebsd] devel/boost: new patch for testing update to 1.39

Alexander Churanov alexanderchuranov at gmail.com
Tue Aug 4 12:28:02 CEST 2009


2009/8/4 Mel Flynn <mel.flynn+fbsd.ports at mailing.thruhere.net>:
>
> I think for the time being PySTE support should be off by default, because it
> pulls in a second libc and databases/akonadi plus kdeedu[34] use boost-python
> and because gccxml looks like a dead project.

Agree.

>
> I've attached a patch that does exactly this and also fixes WITH_DEBUG
> building. There's one issue commented in the Makefile that I'm unable to
> relate to anything I did, but am assuming it's from WITH_DEBUG as well.

The issue was I've accidently hardcoded path which built python
libraries are copied from. As a result, installation success was
depending not only on DEBUG setting, but also on the version of gcc
and, probably, other things.

This is already fixed and checked-in to CVS.

>
> ports/123927 could be solved/prevented by using a WANT_BOOST_PYSTE in
> dependent ports that rely on boost having PYSTE and using PKGNAMESUFFIX plus
> pkg_info to verify if boost-python-libs is boost-python-pyste-libs - as a
> stop-gap.

Well, if the user installs some port that depends on
boost-python-libs, the user gets boost-python-libs installed. Then the
user wants to install another port that depends on
boost-python-pyste-libs. Would this succeed?

Sincerely,
Alexander Churanov,
maintainer of devel/boost-*


More information about the kde-freebsd mailing list