On Tue, 20 Nov 2018 at 13:25, bob prohaska wrote:
[...]
> Is there a resolution to this dilemma, other than just waiting for
> inkscape to catch up? Is it possible to determine which revision of
> the ports tree can make a runnable version of a particular port?
The correct thing to do is to
On Mon, Nov 19, 2018 at 03:57:22PM -0800, bob prohaska wrote:
> Using pkg delete resolved the ImageMagick vs ImageMagic6 conflict, allowing
> inkscape to build successfully from ports on an RPI3.
>
> Alas, I somehow deleted libicuuc.so.62, causing a runtime failure. Rebuilding
> devel/icu got
Using pkg delete resolved the ImageMagick vs ImageMagic6 conflict, allowing
inkscape to build successfully from ports on an RPI3.
Alas, I somehow deleted libicuuc.so.62, causing a runtime failure. Rebuilding
devel/icu got version 63, so that didn't help.
Noticing that inkscape is now
On Wed, 14 Nov 2018 21:06:37 +0900 KIRIYAMA Kazuhiko
wrote:
> er-statement -Wvla -Wpointer-arith -Wmissing-declarations
> -Wmissing-prototypes -Wredundant-decls -Wundef -Wwrite-strings
> -Wformat-nonliteral -Wformat-security -Winit-self -Wmissing-include-dirs
> -Waddress -Wno-multichar
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
