3 ms·
I don't remember enabling iNotify earlier than it was merged in master. Did I miss a build flag that enabled it earlier than I should have? Anyways, I'll use t
by ReAzem 8y ago
I don't remember enabling iNotify earlier than it was merged in master. Did I miss a build flag that enabled it earlier than I should have?
Anyways, I'll use this opportunity to say that it has always been great to work with the guys at Syncthing. They responded quickly to every issue that we have ran into. For example, the switch from FontAwesome to ForkAwesome was done for due to a Debian issue:
- https://github.com/syncthing/syncthing/issues/5236 https://github.com/syncthing/syncthing/issues/5236
- bayindirh 8y agoIIRC, the package description said something similar to "this is the iNotify version of the syncthing binary", or I may be completely wrong. I need to get previous versions and look to the descriptions of each :)
- onli 8y agoYou might mix that up with syncthing-inotify, which was an external small inotify watcher that then pinged syncthing via its API. It was the recommended way to get inotify support till the functionality got merged.
- bayindirh 8y agoMaybe, however all my Debian installations are very strict in their repository configuration, and I'm failing to see syncthing-inotify package in Debian snapshots server [0]. ...or maybe I'm making all these up from all the things I read while researching syncthing, who knows :) Regardless of all, it's working very well and it's dependable now, and it's the point I think :D [0]: https://snapshot.debian.org/package/?cat=s https://snapshot.debian.org/package/?cat=s Addenda: Actually, forgetting all little details about it is a reliable sign of an application working well and just disappears to the background IMHO.