Refresh quietly from the path unit and pacman hook

Add a --quiet mode that updates the pending file without notifying, run by
the new update-notify-quiet.service, so aur sync doesn't notify per package.
This commit is contained in:
Daniele Fucini
2026-10-18 15:31:46 +02:00
parent bd34dd7bf1
commit 41f94d719b
6 changed files with 25 additions and 5 deletions
+5 -3
View File
@@ -43,11 +43,11 @@ systemctl --user enable --now update-notify.timer
The timer runs 5 minutes after boot, then every 6 hours.
A pacman hook also runs update-notify after every pacman transaction, for each logged-in user whose timer is active, so the notification and the status bar file are current right after an upgrade.
A pacman hook also runs `update-notify --quiet` after every pacman transaction, for each logged-in user whose timer is active, so the status bar file is current right after an upgrade.
### Refresh after building packages
Building into a local repository (`aur build`, `aur sync`) doesn't run pacman, so the hook can't catch it. To run update-notify whenever a repository changes, add the repository files to watch to `update-notify.path`:
Building into a local repository (`aur build`, `aur sync`) doesn't run pacman, so the hook can't catch it. To run `update-notify --quiet` whenever a repository changes, add the repository files to watch to `update-notify.path`:
```
systemctl --user edit update-notify.path
@@ -68,11 +68,13 @@ systemctl --user enable --now update-notify.path
## Usage
```
update-notify [threshold]
update-notify [-q|--quiet] [threshold]
```
`threshold` is the minimum number of updates (repo + AUR) before update counts are shown. It overrides the `THRESHOLD` setting below for that run's notification only; the pending file keeps the configured value.
`--quiet` updates the pending file without notifying. Changes to a notification already shown are recorded, so the next timer run doesn't repeat them; a new notification is left for the timer. The pacman hook and `update-notify.path` use it (through `update-notify-quiet.service`), so building or upgrading many packages doesn't notify after each one.
## Configuration
Settings are read from `$XDG_CONFIG_HOME/update-notify/config` (default `~/.config/update-notify/config`), a bash file that is sourced by the script. All settings are optional: