2009/1/12 Jeremy Messenger me...@cox.net
I rather to put only a version and fix the rest port. With that
include/boost-134 hack is going to require hack in every port that depend on
it.
Cheers,
Mezz
Yes, all ports that depend on old boost require modification anyway.
I'm just trying to
2009/1/11 Pav Lucistnik p...@freebsd.org
Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300:
I'll carry out this experiment.
Let's see if there's an easy way to make all the ports respect it, say,
if it would mean just modifying pkg-config output. If it's non-trivial,
we'll have to
Le Dim 11 jan 09 à 0:25:54 +0100, Pav Lucistnik p...@freebsd.org
écrivait :
1) rename devel/boost to devel/boost-134
2) switch all ports depending on devel/boost to devel/boost-134
3) check-in boost-1.37 as devel/boost
4) have enough time to fix applications depending on boost-1.34
2009/1/11 Pav Lucistnik p...@freebsd.org
That's certainly a possibility -- but can two boost versions coexist in
a single system?
That's a real problem. To my mind there are no problems for shared
libraries, but for header files the suggested solution would require placing
headers under
Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300:
2009/1/11 Pav Lucistnik p...@freebsd.org
That's certainly a possibility -- but can two boost versions
coexist in
a single system?
That's a real problem. To my mind there are no problems for shared
On Sun, 11 Jan 2009 12:38:10 -0600, Alexander Churanov
alexanderchura...@gmail.com wrote:
2009/1/11 Pav Lucistnik p...@freebsd.org
That's certainly a possibility -- but can two boost versions coexist in
a single system?
That's a real problem. To my mind there are no problems for shared
2009/1/10 Pav Lucistnik p...@freebsd.org
Are you also willing to fix all the applications that will not work with
the new version of boost?
I understand that's the only concern preventing new boost from being
committed.
Why not fix it in several steps? :
1) rename devel/boost to
Alexander Churanov píše v ne 11. 01. 2009 v 01:07 +0300:
2009/1/10 Pav Lucistnik p...@freebsd.org
Are you also willing to fix all the applications that will not
work with
the new version of boost?
I understand that's the only concern
Hi folks,
The issue ports/129226 was filed at November, 27 2008 and remains open at
present. The issue text contains a link to the patch I've created for the
devel/boost port.
The problem is that current port version is too old. Boost team is going to
release 1.38 on the 31st of January. I have
