ports/146707: devel/boost-* update to 1.43
Alexander Churanov
alexanderchuranov at gmail.com
Wed Jun 9 17:30:06 UTC 2010
The following reply was made to PR ports/146707; it has been noted by GNATS.
From: Alexander Churanov <alexanderchuranov at gmail.com>
To: Max Brazhnikov <makc at freebsd.org>
Cc: bug-followup at freebsd.org, churanov.port.maintainer at gmail.com
Subject: Re: ports/146707: devel/boost-* update to 1.43
Date: Wed, 9 Jun 2010 21:27:57 +0400
Folks,
I suggest checking in slightly different version of the patch. It may
be obtained from
http://alexanderchuranov.com/boost-port/boost-from-1.41-to-1.43_02.diff
The difference is in the order of filenames in pkg-plists, which makes
recent patch smaller and easier to review, because it contains only
changes essential to the update from the upstream. The patch also
handles removal of port patches, which were included into 1.43 and now
unnecessary in ports.
All boost-* ports were tested for correctness: it was verified that
they build, install, deinstall, etc. correctly as suggested in the
handbook.
The following ports, which directly depend on boost, were successfully
build after update:
audio/clementine-player
audio/murmur
cad/salome-kernel
databases/drizzle
deskutils/launchy
devel/crow
devel/libopkele
devel/love
devel/luabind
devel/monotone
devel/srecord
dns/powerdns
dns/powerdns-recursor
editors/xmlcopyeditor
games/alephone
games/blobby
games/flyhard
games/glob2
games/lordsawar
games/mkhexgrid
games/windstille
graphics/enblend
graphics/inkscape
graphics/panomatic
graphics/py-cgkit
graphics/py-visual
graphics/scantailor
irc/ezbounce-devel
math/cgal
net/xorp-devel
www/anyterm
The following ports fail to build both with the 1.41 version of boost
as exists in ports at present and with the updated to 1.43:
cad/salome-geom
cad/salome-gui
cad/salome-med
cad/salome-multipr
cad/salome-sierpinsky
cad/salome-smesh
cad/salome-visu
cad/salome-yacs
devel/guiloader-c++
dns/powerdns-devel
graphics/mapnik
security/botan
Since update does not change the state of directly dependent ports, I
suggest checking it in and handling port failures separately.
Alexander Churanov,
maintainer of devel/boost-*
More information about the freebsd-ports-bugs
mailing list