From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 26E936DE260E for ; Fri, 14 Jul 2017 06:20:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.000] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmU45GRC2qIz for ; Fri, 14 Jul 2017 06:20:19 -0700 (PDT) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTP id 51F456DE25E9 for ; Fri, 14 Jul 2017 06:20:19 -0700 (PDT) Received: from fifthhorseman.net (38.200.broadband6.iol.cz [88.101.200.38]) by che.mayfirst.org (Postfix) with ESMTPSA id B0DC3F999 for ; Fri, 14 Jul 2017 09:20:17 -0400 (EDT) Received: by fifthhorseman.net (Postfix, from userid 1000) id 54BD7203E3; Fri, 14 Jul 2017 15:19:43 +0200 (CEST) From: Daniel Kahn Gillmor To: Notmuch Mail Subject: Re: [PATCH 1/3] config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0 In-Reply-To: <20170714131202.24966-1-dkg@fifthhorseman.net> References: <20170603174754.16911-24-david@tethera.net> <20170714131202.24966-1-dkg@fifthhorseman.net> Date: Fri, 14 Jul 2017 15:19:40 +0200 Message-ID: <87vamv6tqr.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 13:20:20 -0000 --=-=-= Content-Type: text/plain On Fri 2017-07-14 15:12:00 +0200, Daniel Kahn Gillmor wrote: > gmime 3.0 no longer offers a means to set the path for gpg. > > Users can set $PATH anyway if they want to pick a > differently-installed gpg (e.g. /usr/local/bin/gpg), so this isn't > much of a reduction in functionality. see also: https://github.com/jstedfast/gmime/pull/7 > The one main difference is for people who have tried to use "gpg2" to > make use of gpg 2.1, but that isn't usefully co-installable anyway. I think the recommendation for those folks would be something like: mkdir -p ~/bin ln -s $(which gpg2) ~/bin/gpg PATH=~/bin:$PATH though i'm inclined to just suggest that people don't do the "gpg2" co-installable thing at all, since gpg 1.4 and 2.1 diverge on both public keyrings and secret keyrings, and 2.0 is EOL in < 6 months. --dkg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIyBAEBCgAdFiEEOCdgUepHf6PklTkyFJitxsGSMjcFAlloxOwACgkQFJitxsGS MjcQ8w/458q7pU+VjwTw5mePVFMiLOAJY/2WdCPqC16oTepRJYqxdU2T3VfUcc72 Hp2dgL+ArgKagB30Rl3fHuE6lkcEchnejlDESUsRJkResYUjjBMHBfI2XdtNe1FE V9Fa5SBAOWuBBVrzTexupuzzDvQ2SwNkUJSudPtLxakQFWBF++kf02VTHncrnZMs NVPoGdVmO6DRNW3tcdmu4ZTPvoHcUoG7MQLAR5ZXc7JkDpzbR1On6NSsyBHSmx2w 4S9a74gWnp2CuhAwwinFgEvOOWHkSWtiMLn20Gyi4ksC80VqT9kVtFl4AxRdHKVW DcLlPyAtXqUC+6j4Sg1oZVXZ3982SyLo+PEr/pNjVRPtMZ9mDCK0Vltr3HwgvsDa iefOSNtUx+2HQLtMcYVpM/ipCN7m29qkp6WmGtIUMm9tHB7LtuJaPGbxa656n8nZ FWP5WfHduDTZbYs5GInGAE0HoPkQVVQcLZ5EfR9asmK3penI2deX7qv44DEaM1fv FM3100aadep22bzx8n0ms5Yy67pX6+pn/e6BwZfbDMCCpEQZ6dB3blq5EBuBrtoz wvqhYGPs/T99+JKfKA86GnNjegz/NLhvZZy+H9PiGATsE+GzUn3Ck0XiytrCwsI8 rqaejif2CdYw70vl29CyWNc/pX4YXkWEhvn53TccFLfWq9x0Ig== =jdq5 -----END PGP SIGNATURE----- --=-=-=--