diff options
Diffstat (limited to 'desktop/i3lock/i3lock.SlackBuild')
| -rw-r--r-- | desktop/i3lock/i3lock.SlackBuild | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/desktop/i3lock/i3lock.SlackBuild b/desktop/i3lock/i3lock.SlackBuild index a9c54a216f7d3..2493ae5a9db8c 100644 --- a/desktop/i3lock/i3lock.SlackBuild +++ b/desktop/i3lock/i3lock.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=i3lock -VERSION=${VERSION:-2.8} +VERSION=${VERSION:-2.9} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} @@ -69,9 +69,17 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; -# Apply a patch that removes all the PAM-related code, +# This patch reverts a commit that prevents the leakage of information through +# composited notifications. +# That commit causes issues (lag, most notably) on certain compositors. +# See the upstream issue: https://github.com/i3/i3lock/issues/128 +# You're welcome to try to comment this patch out and see whether it just works for you, +# or just leave this as is. +patch -p0 -i $CWD/i3lock-2.9-revert-composite.patch + +# This patch removes all the PAM-related code, # and checks the password against shadow instead. -patch -p1 -i $CWD/i3lock-2.8-no-pam.patch +patch -p0 -i $CWD/i3lock-2.9-no-pam.patch make install DESTDIR=$PKG |