From owner-freebsd-ports@freebsd.org  Wed Nov  2 20:45:56 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CEB8C2BAE6
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Wed,  2 Nov 2016 20:45:56 +0000 (UTC)
 (envelope-from stdin@niklaas.eu)
Received: from mx.box-hlm-03.niklaas.eu (mx.box-hlm-03.niklaas.eu
 [IPv6:2a02:2770:15:0:21a:4aff:feaa:e902])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 71AF415D8;
 Wed,  2 Nov 2016 20:45:55 +0000 (UTC)
 (envelope-from stdin@niklaas.eu)
Received: from box-hlm-03.niklaas.eu (mysql2.box-local.klaas [10.77.5.3])
 by mx.box-hlm-03.niklaas.eu (Postfix) with ESMTPSA id 6C0DB4F999D;
 Wed,  2 Nov 2016 21:45:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=niklaas.eu;
 s=default; t=1478119551;
 bh=MfyawjnCEo2dmvQuEAm297ti5pfGPOpDv74Xewg4RK4=;
 h=Date:From:To:Cc:Subject:Reply-To;
 b=l4VGX/kSDJW32HD//81SaJvqCoDY8WZeQ0TfCT6nTwiyEJvwpwjPJiF34pkKTFcNX
 Bmn07hsxdRD9fJAwNoprci3lkKVP0UPOiQFK7o2d2CUE/Tpb36xo+ksQutoic6rxGg
 l7NxvMPtKAWZArvJJRDdgm+6Fzr7NineDiBrMU/A=
Date: Wed, 2 Nov 2016 21:45:51 +0100
From: Niklaas Baudet von Gersdorff <stdin@niklaas.eu>
To: freebsd-ports@freebsd.org
Cc: bapt@freebsd.org, dereks@lifeofadishwasher.com
Subject: mail/{neo,}mutt: why not packaged with gpgme?
Message-ID: <20161102204551.jkismaljloqwlokp@box-hlm-03.niklaas.eu>
Reply-To: stdin@niklaas.eu
Mail-Followup-To: freebsd-ports@freebsd.org, bapt@freebsd.org,
 dereks@lifeofadishwasher.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: NeoMutt/20161003 (1.7.0)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2016 20:45:56 -0000

Hello,

While talking about an issue I have with mail/{neo,}mutt and
security/gnupg on #gnupg on freenode I was advised to use
security/gpgme with mutt. I haven't been using gpgme for a while,
mainly because the packaged versions of both mail/{neo,}mutt have
it disabled and I was too lazy to compile it on my own. Since
I got that advice, I've started wondering:

Why is gpgme disabled by default?

As was argued (and as I experienced myself) setting up mutt to
work with gpgme is much easier than without. Especially gnupg2
made it difficult to configure mutt without gpgme. So why not
enabling gpgme in the packaged versions?

I decided not to create a PR about this request. If that's wrong,
tell me and I'll create one.

    Niklaas