From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:50210) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gdEFs-0001Z4-Aj for guix-patches@gnu.org; Sat, 29 Dec 2018 08:02:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gdEFg-0005wz-PK for guix-patches@gnu.org; Sat, 29 Dec 2018 08:02:11 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:44654) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gdEFf-0005w0-Rq for guix-patches@gnu.org; Sat, 29 Dec 2018 08:02:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gdEFe-0006oN-DD for guix-patches@gnu.org; Sat, 29 Dec 2018 08:02:03 -0500 Subject: [bug#33888] [PATCH] gnu: Add sway. Resent-Message-ID: Date: Sat, 29 Dec 2018 14:01:07 +0100 From: Rutger Helling Message-ID: <20181229140107.4d93b852@mykolab.com> In-Reply-To: <20181227160503.2d059a36@mykolab.com> References: <20181227160503.2d059a36@mykolab.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/61O2Fx4e8E8EaF10r6oo0HT"; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 33888@debbugs.gnu.org --Sig_/61O2Fx4e8E8EaF10r6oo0HT Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I've been told that the Sway developers don't want this release packaged. And it unfortunately also depends on staging, which I missed. Having said that, if there are no objections I'd like to merge this once it hits 1.0 and staging is merged. On Thu, 27 Dec 2018 16:05:03 +0100 Rutger Helling wrote: > Hey Guix, >=20 > these patches add Sway. >=20 > Note that with > (screen-locker-service sway "swaylock") > we should now have a native Wayland screen locker. >=20 > Supposedly this can be done without making the swaylock binary SUID, > but I've been unable to figure out how. --Sig_/61O2Fx4e8E8EaF10r6oo0HT Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEAVThuRzJ2e93ZI3n86cn20T8yjYFAlwncBMACgkQ86cn20T8 yjZGaAf/ZBfYaAPCMFMKDiibHPpsoaVJ7uUYwJSXv8Gog3rbdx41pXEMhXbxZTYa pbBvLf3aRtUapKNn0Z+fW5i1JlZz/F6LCui/vNy8/m6q6dzkx7HmkloYI7sgBzaM PIj/9KmZoMSRhbbnRoKpTt6HFYI9YOQKag1JKJSndGQ7BapO/fyxoy8bEFTSMm2G CKfdgBvnbdcXdI+l4Dm0b7rAEZQWpCVArnjfX7V79bFZOFr49K38MdfEx4ekfDl0 iG+4bll8xHdxZfE+HhsfdEjzjXhA20iP+s5ZINZftBDd8yNSyyVzR3MsJkRggyvz Oex4M6mc+9ZmnOysXQi9UXwXndBFSw== =NR+r -----END PGP SIGNATURE----- --Sig_/61O2Fx4e8E8EaF10r6oo0HT--