fresh devel/boost

Alexander Sack pisymbol at
Mon Mar 2 08:19:18 PST 2009

On Mon, Mar 2, 2009 at 9:30 AM, Andriy Gapon <avg at> wrote:
> I've seen couple of conversations in this list about updating devel/boost to the
> recent version. As I understand people already have patches but the main issue is
> getting all ports depending on boost to work with the new version, and testing this.
> Now I am thinking - why not create a boost-devel or something like that port, or
> move current boost to boost_1_34. This would immediately provide recent boot to
> all and give time for dependent ports to be switched over (if needed at all).
> I believe that something like the following
> configure --libdir=${LOCALBASE}/lib/boost/1.38.0
> --includedir=${LOCALBASE}/include/boost/1.38.0
> should allow multiple boost versions to co-exist.

I'm actually shocked that there are THAT MANY ports that:

-  Need boost to begin with
-  And if they need boost, need boost-1.34 specifically, i.e. they
will break with 1.38

Minimally one could create a boost-1.38 or boost-devel if the above
regression testing is THAT horrific.   Other than long double support,
the current boost release builds basically out of the box and only
minor updates to the current boost infrastructure are needed.  I have
an updated boost-1.38 port in my directory for a little while now (I
have actually dig it up).

But just leaving at 1.34 is pretty awful given the great changes and
additions to boost in the last couple of dot releases (ASIO support
comes to mind).



More information about the freebsd-ports mailing list