There is a regression with the 5.1.2 update to giflib. This affects the
ability for applications to render gif images usually ocurring after the
first gif image is rendered. Upstream has been notified but has not yet
provided feedback.
giflib 5.1.2 was a security fix, so reverting is not reasonable.
"The removed check look redundant - I couldn't find a code path where
Private->RunningBits would exceed that limit after initialization.
(Currently Private->RunningBits is checked before it is initialized)."
PR: 207849
Submitted by: Stefan Ehmann <shoesoft@gmx.net>
Approved by: ports-secteam (with hat)
MFH: 2016Q1
There were reports of fallout so this has been reverted. It is not
understood why an explicit PATH needs to be set. In testing without it
the correct PATH appears to be exported during the start_precmd routine.
PR: 207583
Approved by: maintainer
Changes:
http://www.ogdf.net/doku.php/tech:versions#v_201505_baobab
- Remove dependencies on math/abacus and math/coinmp, as they are
now bundled into the OGDF source tarballs and compiled from there
(COIN remains optional)
- Point MASTER_SITES to the official OGDF website
- Utilise USES=compiler:features to detect C++11 support, and
add compiler flags -std=c++11 if so (required for build to complete
without errors)
- Remove custom do-install recipe, and instead use default
make install target
- Take maintainership
PR: 207531
Submitted by: Ben Woods <woodsb02@gmail.com>
In preparation for the upcoming KDE Frameworks 5 and Plasma 5 ports, install
attica's headers into include/attica/attica instead of include/attica.
Users of attica reference the headers in the code with
#include <attica/foo.h>
which means the compiler is passed -I${LOCALBASE}/include for the headers to
be found.
The KDE Frameworks 5 version of attica installs the headers into
include/KF5/attica, so depending on the other of the arguments the compiler
can end up being passed
-I${LOCALBASE}/include -I${LOCALBASE}/include/KF5
leading to the wrong attica headers being used instead.
By changing the header location, we make sure one passes
-I${LOCALBASE}/include/attica to use the attica 0.4.2 headers.
The original idea and code came from Tobias Berner <tcberner@gmail.com>,
with further improvements from myself.
While here, add some comments explaining why some sed calls are made in the
post-patch target.
Last but not least, audio/tomahawk had to be patched for the attica headers
to be properly found now that they are no longer in ${LOCALBASE}/include.
The patch itself contains a larger explanation of what had to be done. All
other ports depending on x11-toolkits/attica work fine without any changes.
Submitted by: Tobias Berner <tcberner@gmail.com> (original version)
Two minor bug fixes:
* A specific check during test mode would emit a failure to stdout when
testing devel/py-setuptools27. It turns out that there's a file there
with a space in the filename. The filename was an argument for
/usr/bin//file and it wasn't escaped. The file in question had
parentheses too which the shell was trying to process. The fix was
to escape the filename in the /usr/bin/file command.
* The builders were mounting the source directory from "/usr/src", not
$sysroot/usr/src as intended. This potentially causes breakage when
the $sysroot reflects a different versions/release than the host
machine has (e.g. making FreeBSD 10.2 packages on FreeBSD 11-current).
Now the source directory mount is relative to profile's $sysroot.
