Status of devel/boost upgrade

[Jeremy Messenger]

On Tue, 31 Mar 2009 17:02:46 -0600, Dmitry Marakasov <amdmi3 at amdmi3.ru>
wrote:

> Hi!
>
> By the way, I've just ran into this sample of code in www/openvrml:
>
> .if exists(${LOCALBASE}/include/boost/python.hpp)
> LIB_DEPENDS+=	boost_python.4:${PORTSDIR}/devel/boost-python
> .else
> LIB_DEPENDS+=	boost_regex.4:${PORTSDIR}/devel/boost
> .endif
>
> and thought: why don't we create something like bsd.boost.mk so porters
> don't have to invent a bicycle and add custom check for boost, and users
> don't run into conflicts.
>
> Actually, it's going to be too little stuff there, so it may be
> just included into port.mk, but I'd split it out for modularity.
> The idea:
>
> ports:
> USE_BOOST=	yes|python


No need bsd.boost.mk over that small stuff. How about resolve conflict for
real by split boost and boost-python by have boost only install non-python
stuff and boost-python install only python stuff? The USE_BOOST isn't
going to solve anything either because the boost-check-python still stop
and tell it's conflict.

Cheers,
Mezz

> port.mk:
> .if defined(USE_BOOST)
> .include "${PORTSDIR}/Mk/bsd.boost.mk"
> .endif
>
> bsd.boost.mk:
>
> .if defined(USE_BOOST) && ${USE_BOOST} == "python"
> LIB_DEPENDS+=	boost_python:${PORTSDIR}/devel/boost-python
> do-configure:	boost-check-python
> .elif defined(USE_BOOST)
> LIB_DEPENDS+=	boost_thread:${PORTSDIR}/devel/boost
> .endif
>
> boost-check-python:
> .if !exists(${LOCALBASE}/include/boost/python.hpp)
> 	@${ECHO_MSG} "This port requires boost built with python support."
> 	@${ECHO_MSG} "Please uninstall boost and install boost-python."
> 	@${FALSE}
> .endif


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org