From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:58453) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gydn6-0003Cx-B0 for guix-patches@gnu.org; Tue, 26 Feb 2019 09:33:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gydn4-0002FJ-OS for guix-patches@gnu.org; Tue, 26 Feb 2019 09:33:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:38835) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gydn4-0002F1-Jw for guix-patches@gnu.org; Tue, 26 Feb 2019 09:33:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gydn4-000362-8A for guix-patches@gnu.org; Tue, 26 Feb 2019 09:33:02 -0500 Subject: [bug#34644] [PATCH] gnu: Add xsane. Resent-Message-ID: Date: Tue, 26 Feb 2019 15:32:06 +0100 From: Danny Milosavljevic Message-ID: <20190226153206.738165fa@scratchpost.org> In-Reply-To: <87sgwblbnb.fsf@nckx> References: <20190225012502.7244-1-me@tobias.gr> <87tvgrefz5.fsf@GlaDOS.home> <87sgwblbnb.fsf@nckx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/0JQQP5XJSNYPAN6vY7=7Bwo"; 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: Tobias Geerinckx-Rice Cc: 34644@debbugs.gnu.org, Diego Nicola Barbato --Sig_/0JQQP5XJSNYPAN6vY7=7Bwo Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, On Mon, 25 Feb 2019 23:57:12 +0100 Tobias Geerinckx-Rice wrote: > Nor I. It's an interesting situation: snprintf.c seems to have=20 > been re-(dual-)licenced under both Artistic and GPL2+OpenSSL=20 > exception. >=20 > However, the version shipped with xsane is older (perhaps xsane=20 > itself is, even). >=20 > I guess we can just do what Trisquel does and replace it with a=20 > newer version. Sure. > There's also some talk of a =E2=80=99system snprintf=E2=80=99 that=20 > may or may not do the job without having to provide our own=20 > replacement. If we did that we should mention it upstream--maybe their implementation has special features that they require that a system implementation would not have. --Sig_/0JQQP5XJSNYPAN6vY7=7Bwo Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlx1TeYACgkQ5xo1VCww uqVh3Af/fAHuEIGenVmaCGsWGSuIL7b8pvXM1oZT79vVGPabVlPL5JPemhMZD1ry MIO6ydkCqq3XHsz10S7TSz1aeOluDAC4HhxYnSg5rGiXTk1RMXTB0Vmw8O5yqDb0 IBQvR+qmIp0gZrqnctDNQVFR76h9GDsN6Gmj1QiPenjCpUnA/2Lomvt+8ox1F0EJ hnu8nWja25E0YB/0kqueBc0SRz512GADVhkqgls1Kkn3T/xzEZkY4PgAnfRAATcp uyZuhprfm56t4OTcn0+SM3wIEhLUUAh4jgr8Pqgd0oZn/V4Ruc7sDwfiBik5/KgP inqj8zIBx5UMNzN6EGnAXydg8HkFvg== =43dE -----END PGP SIGNATURE----- --Sig_/0JQQP5XJSNYPAN6vY7=7Bwo--