Repository navigation
Scour 0.2.0-alpha.5 — changes inside new folder trees are seen as they happen
Pre-release
Pre-release
Pre-release. A fix worth having: if you installed 0.2.0-alpha.4, update. Tested on one Linux machine in daily use; the packages were installed in clean Debian 11 and 12, Ubuntu 22.04 and 24.04 and Fedora containers, where the service indexed and found a file and every face answered. The Windows zip builds; this release has not been started on Windows.
What changed since 0.2.0-alpha.4
- Changes inside a folder tree made all at once are seen as they happen. When an archive was unpacked, a repository cloned, packages installed or
mkdir -prun, only the top folder of the new tree was being watched by name: every later change in the folders inside it — a file added, grown or deleted — went unseen until the daily check, a day or two later. On the development machine that check found over seventy thousand such files in a day. Every folder of a new tree is now learned as it appears.
Checked with three 60,000-file archives unpacked and removed at once, six times over: a new file elsewhere was found within seconds every round, and nothing of the removed trees was left in the index.
Installing
- The tarball's
install.shneeds no password. It installs the binaries, the menu entry, the icon and the GNOME Shell extension, binds Super+F, and at a terminal offers to start the service with your session. .deband.rpmpackages, all seven binaries. Installing starts nothing;systemctl --user enable --now scourd.servicedoes, and any face starts the service itself when it finds none.- Watching changes as they happen needs a privileged helper, once: from the tarball,
sudo bash packaging/install-service.sh; with a package, the steps are in/usr/share/doc/scour/PACKAGE-NOTES. Without it nothing is missed, but a change is found by walking when the disk's write counter moves, which is slower. - The Linux binaries are built against glibc 2.30: Debian 11, Ubuntu 22.04, RHEL 9 and later.
sha256sum -c SHA256SUMSchecks the downloads.
Known limits
- Raising an open window, and the file manager's, needs the GNOME extension. Log out and back in once after installing — GNOME loads a new extension at login.
- The window cannot drag files out; Copy the file and paste does the same. The browser window can.
- One account per service instance; the tarball's
install-service.shadds a second. - Inside a Flatpak nothing is watched live; the service finds changes from the volume's write counter and its periodic pass.
- The index format may change between releases.