Qt tests now pass for me too.

Thanks. The latest upload fixes those tests for me, all 8 pass.

I pushed changes that allow testing glib's file monitoring: https://github.com/arrowd/freebsd-ports/tree/inotify-test

In D50315#1150050, @markj wrote:

Do you know offhand if there is much use for fanotify() compatibility? I'm wondering how widely used it is vs. inotify.

In D50315#1149915, @markj wrote:

From my reading of Linux inotify docs, IN_ACCESS should only be generated for objects within a watched directory, not for the watched directory itself. So, this test seems to contradict the documentation, and my implementation follows the documentation here. Which one is right? I don't have quick access to a Linux system to test.

I patched libinotify-kqueue to call into the native implementation and then ran its tests. Some of them are failing, here's the log

Hmm, does a clean build work?

I tried building it with make buildworld && make buildkernel and it failed with

--- libsys.so.7.full ---
Building shared library libsys.so.7
...
ld: error: version script assignment of 'FBSDprivate_1.0' to symbol '_inotify_add_watch' failed: symbol not defined
ld: error: version script assignment of 'FBSDprivate_1.0' to symbol '__sys_inotify_add_watch' failed: symbol not defined
ld: error: version script assignment of 'FBSDprivate_1.0' to symbol '_inotify_rm_watch' failed: symbol not defined
ld: error: version script assignment of 'FBSDprivate_1.0' to symbol '__sys_inotify_rm_watch' failed: symbol not defined
cc: error: linker command failed with exit code 1 (use -v to see invocation)

So, while I am still not sure what problem we're solving here, this what I came up with:

What are consumers of this port?

Now that distinfo's are separated, why do we need this autogen stuff at all?

LGTM as well.

Because the structure of the ports itself is changed in non-trivial way.

Why bump PORTREVISIONs? There should be no visible changes in the resulting package.

I'm still baffled about what's the problem with all these distinfos. Decoupling nvidia-driver-XXX distinfos looks like a good idea to me, so maybe we should start with that?

• Rebase and update

Can you please show commands that are causing the problem that this change tries to solve? It feels like there should be a simpler solution.