Will

AFAICT there are two ways to do this with fanotify. (ebpf could also do this in different ways.) Both of our solutions need to know whether or not some given...

I'll investigate how inotifywait does this. I also wonder if there's a way we can use `FAN_MARK_FILESYSTEM` to our advantage in some cases: > FAN_MARK_FILESYSTEM (since Linux 4.20) > Mark...

Should we add something like that last bit into this project's CMake file as well? > ```include_directories(${wtr.watcher_SOURCE_DIR}/watcher-c/include)```

Python bundles it into the package and loads it with dlopen at runtime; Node/Javascript is a native addon, which seems to be kind of (exactly?) a shared library, and it's...

I’m open to preferring (or mandating) that a global system library is used, but there are some tradeoffs - Unintentionally breaking backwards compatibility is a pain. Versioning the shared libraries...

> So they ship their own .so or compile it at install? Python ships its own .so, node/js *is* a “native addon” (no libwatcher-c.so involved)

> Maybe could we have both? Bindings could check if a global installation is available, and fallback on a local install if it's not the case? Yeah, that sounds good...

Node and Rust could prefer a system library at build-time with some careful linker arguments. I need to see how exactly libraries are resolved currently if identically named libwatcher-c's exist,...

> Maybe the watcher could say that in the self/live event? I've been hesitant to add that because the primary use is debugging (IOW, I'm hesitant to add any debugging...

> Is the associatedPathName of a symlink supposed to be the target? Yes