|Summary:||Port Update: devel/boost-*|
|Product:||Ports & Packages||Reporter:||Jordan Irwin <antumdeluge>|
|Component:||Individual Port(s)||Assignee:||FreeBSD Office Team <office>|
|Severity:||Affects Only Me||CC:||antumdeluge, office, pi|
Description Jordan Irwin 2014-08-09 21:24:33 UTC
Update available for Boost libraries. New upstream version: 1.56.0. Current ports version 1.55.0. Ports affected (I think): devel/boost-all devel/boost-docs devel/boost-jam devel/boost-libs devel/boost-python-libs http://sourceforge.net/projects/boost/
Comment 1 Jordan Irwin 2014-08-09 21:25:21 UTC
Comment 2 John Marino 2014-08-09 22:30:16 UTC
Jordan, I'm assigning this to the maintainer as well, but I am curious about the motivation. Do you realize that each time boost is updated, dozens of ports break? The fact that office@ owns it tells me openoffice / libreoffice are also sensitive the version. I think at the very least you are looking a an EXP-RUN to figure out what the damage would be. So that said, why are proposing to the boost maintainer to update this before they feel it's necessary? Like I said, I am mainly curious. There's no wrong answer.
Comment 3 Jordan Irwin 2014-08-09 22:44:31 UTC
No, I didn't know that it caused port breaks. I simply got an email notification from SF that Boost had been updated. So I thought I would notify the maintainer about it. Perhaps it would be better for me to email maintainers directly rather than post to bugs for updates?
Comment 4 John Marino 2014-08-09 22:48:07 UTC
PRs are cheap and public, and appropriate if you have patches. If it's just "hey, there's a newer version available" then PRs are not appropriate. Especially if it's on sourceforge, the maintainers already know about updated versions availability because portscout sends an email and tracks it. Anyway, it's fine. office@ knows now and can close the PR if they want.
Comment 5 Jordan Irwin 2014-08-09 22:49:47 UTC
Okay, thanks. From now on if I feel the need to contact a maintainer about updates I will do so directly.
Comment 6 Baptiste Daroussin 2014-08-26 05:55:07 UTC
boost is always a big beast to upgrade, and we do try to upgrade it with caution. 1.56.0 will happen but we first need to determine what is breaks :)
Comment 7 John Marino 2015-02-13 14:37:00 UTC
1.57 is out now. 1.55 cannot be built with gcc-5 without patches due to c++11 errors. Can office@ think about upgrading? 1.57 is one year ahead of 1.55. For boost, that's a long time.
Comment 8 Kurt Jaeger 2015-04-16 14:20:09 UTC
The upgrade is being worked on in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198751