Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mate-screensaver: update to 1.22.1.
Date: Fri, 20 Sep 2019 03:10:30 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14599@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

There is a new pull request by thomas-t-w against master on the void-packages repository

https://github.com/thomas-t-w/void-packages mate-screensaver
https://github.com/void-linux/void-packages/pull/14599

mate-screensaver: update to 1.22.1.
Switch from consolekit to elogind.

I disabled consolekit explicetly due to #ifdefs in gs-listener-dbus.c
No need to explicetly enable elogind in configure. Elogind ships a /usr/lib/pkgconfig/libsystemd.pc and a relevant simlinked include directory. Mate screen saver sources actually reuse the systemd #ifdef for elogind anyways.
This was tested by closing and opening laptop lid as well as "loginctl lock-session".

A patch file from https://github.com/void-linux/void-packages/pull/14599.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mate-screensaver-14599.patch --]
[-- Type: text/x-diff, Size: 1554 bytes --]

From e3b43b55e819843964bd2f7fe2b558d0a19dec7d Mon Sep 17 00:00:00 2001
From: Thomas <thomasw@fastmail.cn>
Date: Thu, 19 Sep 2019 18:46:31 -0400
Subject: [PATCH] mate-screensaver: update to 1.22.1.

Switch from consolekit to elogind.
---
 srcpkgs/mate-screensaver/template | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/mate-screensaver/template b/srcpkgs/mate-screensaver/template
index 86e616a4a01..9d6c29a64c6 100644
--- a/srcpkgs/mate-screensaver/template
+++ b/srcpkgs/mate-screensaver/template
@@ -1,18 +1,20 @@
 # Template file for 'mate-screensaver'
 pkgname=mate-screensaver
-version=1.22.0
-revision=2
+version=1.22.1
+revision=1
 build_style=gnu-configure
+configure_args="--without-console-kit"
 hostmakedepends="pkg-config intltool itstool glib-devel"
 makedepends="dbus-glib-devel libnotify-devel libXScrnSaver-devel
- libmatekbd-devel mate-menus-devel mate-desktop-devel pam-devel"
+ libmatekbd-devel mate-menus-devel mate-desktop-devel pam-devel
+elogind-devel"
 depends="mate-desktop mate-session-manager"
 short_desc="Screensaver for MATE"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later, LGPL-2.0-or-later"
 homepage="https://mate-desktop.org"
 distfiles="https://pub.mate-desktop.org/releases/${version%.*}/${pkgname}-${version}.tar.xz"
-checksum=5e0b043570dfc1904e9892956ec8377261f94ed541b7dafde22010a619f3dd9d
+checksum=6cef439cb9885df08769500b87df441a0777a6f08bd6f920fad92dfd75c19830
 
 post_install() {
 	vinstall ${FILESDIR}/${pkgname}.pam 644 etc/pam.d ${pkgname}

             reply	other threads:[~2019-09-20  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20  1:10 voidlinux-github [this message]
2019-09-21 12:15 ` [PR PATCH] [Merged]: " voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14599@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).