maintainer-feedback requested: [Bug 249319] x11-toolkits/vte3: fail to build "Dependency fribidi found: NO found 0.19.7 but need: '>=1.0.0'"

[bugzilla-noreply at freebsd.org]

Bugzilla Automation <bugzilla at FreeBSD.org> has asked freebsd-gnome (Nobody)
<gnome at FreeBSD.org> for maintainer-feedback:
Bug 249319: x11-toolkits/vte3: fail to build "Dependency fribidi found: NO
found 0.19.7 but need: '>=1.0.0'"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249319



--- Description ---
This version of vte3 require fribidi >= 1.0.0:

Dependency fribidi found: NO found 0.19.7 but need: '>=1.0.0'
Found CMake: /usr/local/bin/cmake (3.18.2)
Using 'CMAKE_PREFIX_PATH' from environment with value: '/usr/local'
Using 'LDFLAGS' from environment with value: ' -fstack-protector-strong '
Run-time dependency fribidi found: NO (tried cmake)

meson.build:414:2: ERROR: Invalid version of dependency, need 'fribidi'
['>=1.0.0'] found '0.19.7'.

A full log can be found at
/tmp/work/usr/ports/x11-toolkits/vte3/work/vte-0.60.3/_build/meson-logs/meson-l
og.txt
===>  Script "configure" failed unexpectedly.
Please report the problem to gnome at FreeBSD.org [maintainer] and attach the
"/tmp/work/usr/ports/x11-toolkits/vte3/work/vte-0.60.3/_build/meson-logs/meson-
log.txt"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
===========================================================================

There is fribidi 1.0.10 already: https://github.com/fribidi/fribidi/releases
But a lot of ports depends on it.

FriBidi Version 1.0.0
@dov dov released this on 4 Feb 2018 · 122 commits to master since this release
Version 1.0.0 of FriBidi is a major update that adds support for all the
changes to the Unicode Bidirectional Algorithm that were introduced in UAX#9,
version 6.3, and beyond. This library contains test code that validates the
algorithm against the test-files provided by the Unicode consortium, and have
been verified to be 100% compliant with version 10 of the unicode algorithm.
Because of changes to the algorithm, the previous API have been deprecated in
favor of a new API that introduces another couple of parameters. But the old
API has been retained, and will return the same results as before these
algorithmic changes.

Look like it's compatible.