User Details
- User Since
- Oct 23 2016, 10:57 AM (450 w, 2 d)
Today
Yesterday
Sun, Jun 8
Sat, Jun 7
Yep, I messed up and it was still using libinotify's libinotify.h. I've redone the test properly and found that the program starts behaving differently if linked to libinotify.
Fri, Jun 6
Would it be possible to make native sys/inotify.h be a drop-in replacement for libinotify's one? In other words, I want a program that was compiled against /usr/include/sys/inotify.h to work when run with LD_PRELOAD=libinotify.so. This will provide an almost painless transition from libinotify to the native implementation.
Thu, Jun 5
Wed, Jun 4
Tue, Jun 3
Mon, Jun 2
Why was this abandoned?
Ping.
Sun, Jun 1
Sat, May 31
Ugh, I guess you're right. So we need to make sure that no libinotify-kqueue is installed on a native intofy-enabled system.
Now we need to figure how to handle a conflict with libinotify-kqueue. The problem can be observed with taking the main branch of Ports and running
Yes, works for me too now and the performance is on par with other implementations.
Fri, May 30
Thu, May 29
Wed, May 28
Qt tests now pass for me too.
Tue, May 27
Sun, May 25
Sat, May 24
Thanks. The latest upload fixes those tests for me, all 8 pass.
Fri, May 23
Thu, May 22
I pushed changes that allow testing glib's file monitoring: https://github.com/arrowd/freebsd-ports/tree/inotify-test