Félix Saparelli
Félix Saparelli
Can you explain what you mean by > Also to make the configuration more complete I was thinking of exposing a `Fn(&Path)->WalkDir`
- What I mean by "wondering whether adding a variant to that enum would really be a breaking change" is that `RecursiveMode` is never returned from the API, so there's...
Right, sounds good.
This looks good, I like this. On Mon, 18 Feb 2019 at 09:14, vemoo wrote: > I have it mostly working for inotify ( > https://github.com/vemoo/notify/tree/watch-filter). There's 1 test (...
I should have my mac back from the 23rd onwards, so I'll be able to help thenre. On Mon, 25 Feb 2019, 08:09 vemoo, wrote: > I'm slowly making progress....
That would entail writing a completely new backend that doesn't use inotify at all, right? It's... certainly possible, but non-trivial at this point. (It will be somewhat easier in vNext.)
Notify also already exposes inotify's IN_ATTRIB events (as Op::CHMOD).
> Correct, but chmod only does general file permissions. No, I mean, this library translates `IN_ATTRIB` _to_ `Op::CHMOD`. (There was a call to rename that event `Op::METADATA` to indicate that...
> Yes, agreed. Ah, alright. > So would it be possible to change it to Op:METADATA in v5? There's no need. V5 has a different event classification design so it...
> ...could have an optional dependency on auditd for Linux, and compare inotify triggers with auditd logs... Ahh, totally. At a logistics level, the way this would go (and could...