fuxino/update-notify
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove the pacman hook

Browse Source 
Status bars already drop installed entries, and the path unit covers repo
builds, so the hook only ran checkupdates on every transaction.
This commit is contained in:
Daniele Fucini
2026-10-18 15:47:33 +02:00
parent 69450e4a3c
commit 10b84b771e
5 changed files with 4 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -5
View File
@@ -43,11 +43,9 @@ 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 --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 --quiet` whenever a repository changes, add the repository files to watch to `update-notify.path`:
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
@@ -73,7 +71,7 @@ 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.
`--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. `update-notify.path` uses it (through `update-notify-quiet.service`), so building many packages doesn't notify after each one.
## Configuration
@@ -105,7 +103,7 @@ aur <pkg> <newver>
kernel <custom-pkg> <stock-ver>
```
The file reflects the last run, which the pacman hook and `update-notify.path` keep close to current. To keep a bar current in between, drop entries whose installed version (`pacman -Q`) is no longer older than `newver`, or, for `kernel` lines, whose custom build has caught up with `stock-ver` (ignoring `pkgrel`). This only reads local data, so it's cheap to run often.
The file reflects the last timer or `update-notify.path` run. To keep a bar current in between, e.g. right after an upgrade, drop entries whose installed version (`pacman -Q`) is no longer older than `newver`, or, for `kernel` lines, whose custom build has caught up with `stock-ver` (ignoring `pkgrel`). This only reads local data, so it's cheap to run often.
## License