| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-10-17 | Updated to 6.08 | Vryali | |
| 2023-01-02 | Updated to 6.06 and fixed conflicts with xfce4-xscreensaver | Vryali | |
| 2022-06-09 | Updated version and changed configure from with-x-app-defaults to ↵ | Vryali | |
| with-app-defaults (new param name) | |||
| 2022-04-19 | Modified to 6.03 - did some clean-up as per namcap and modified deps | Vryali | |
| 2021-10-01 | 6.01 | xdavidwu | |
| 2021-04-08 | 6.00 | xdavidwu | |
| 2021-02-22 | 5.45 | xdavidwu | |
| 2020-09-12 | bump pkgrel | xdavidwu | |
| 2020-09-11 | Add contributor line to PKGBUILD comment | Christopher Pence | |
| 2020-08-30 | Fix migration template xscreensaver-config.xsl | Christopher Pence | |
| xscreensaver-config.xsl defines .desktop entries for an xscreensaver backend, but it sets the executable parameters as: TryExec=zoom Exec=zoom -root These reference the screensaver's executable ("zoom") by a relative path. If there's a conflicting executable on the machine (e.g. zoom, the popular video conferencing app), then that other executable would be run instead of the screensaver when the screen blanks. Using an absolute path removes the ambiguity: TryExec=/usr/lib/xscreensaver/zoom Exec=/usr/lib/xscreensaver/zoom -root This commit adds absolute paths, on top of: - Rewrites some of the template to use variables and concat() on input strings. - Adds `Hidden=true` to avoid adding the screensavers as application menu items. | |||
| 2020-03-23 | updated to 5.44 | xdavidwu | |
| 2019-03-20 | update to 5.42 | xdavidwu | |
| 2018-11-09 | remove pam config | xdavidwu | |
| 2018-11-09 | init commit | xdavidwu | |