Asger Geel Weirsøe
1934b86c13
A second AUR package with the same release prebuilt. The workflow builds the tag into a staged meson install tree (--prefix=/usr, no update check), names the tarball after its sha256 so a published name never changes bytes, uploads it to asger.weirsoe.dk/tarballz with a key that may only write ahfail-* tarballs, checks that the public URL serves the same bytes, and only then pushes ahfail-bin to the AUR. A manual run can now publish source, bin or both. Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
30 lines
875 B
Plaintext
30 lines
875 B
Plaintext
_ahfail_msg() {
|
|
cat <<'MSG'
|
|
==> ahfail is its own screen locker and uses its own PAM service (/etc/pam.d/ahfail).
|
|
Nothing in your other PAM files has been changed.
|
|
|
|
Check your setup: ahfail doctor
|
|
See the effect safely: ahfail test
|
|
Lock the screen: ahfail
|
|
|
|
Lock automatically:
|
|
Wayland: swayidle -w timeout 300 'ahfail' before-sleep 'ahfail'
|
|
X11: xss-lock -- ahfail
|
|
|
|
The old PAM hook (auth optional .../libahfail_pam.so in e.g. /etc/pam.d/i3lock)
|
|
is no longer needed with `ahfail`. Remove that line yourself if you added it.
|
|
MSG
|
|
}
|
|
|
|
post_install() {
|
|
_ahfail_msg
|
|
}
|
|
|
|
post_upgrade() {
|
|
# Only when coming from before 0.10.0, when ahfail became its own locker;
|
|
# repeating the message on every update would just teach people to skip it.
|
|
if (( $(vercmp "$2" 0.10.0) < 0 )); then
|
|
_ahfail_msg
|
|
fi
|
|
}
|