Date: Tue, 04 Sep 2007 13:52:11 +0200 From: Michael Nottebrock <lofi@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: cvs-ports@freebsd.org, cvs-all@freebsd.org, linimon@freebsd.org, Roman Bogorodskiy <novel@freebsd.org>, ports-committers@freebsd.org Subject: Re: cvs commit: ports/security/gnupg Makefile Message-ID: <46DD46EB.2020605@freebsd.org> In-Reply-To: <alpine.BSF.0.9999.0709031352120.31928@ync.qbhto.arg> References: <200709021108.l82B8Axp085777@repoman.freebsd.org> <alpine.BSF.0.9999.0709021304590.54479@ync.qbhto.arg> <20070903051037.GA27386@underworld.novel.ru> <alpine.BSF.0.9999.0709031352120.31928@ync.qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA91514826DBD862CA6A840CE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Doug Barton schrieb: >> >> OPTIONS would be reasonable in this case. We can enable ncurses backen= d >> by default and user will be able to configure the port to make it use >> other backends he/she wants. > > That is basically what I had in mind. I'd like to hear from lofi, but > my offer to help with that is still good. Security/pinentry is an "old school" master-port for the pinentry-[toolkit] slave-ports. I stopped doing master-slave ports of that sort after that one precisely because you end up in situations like this where people manage to miss the ports they are supposed to use despite the fact they are being pointed to them in pkg-messages and they can be very easily found in a search. Apparently even committers sometimes cannot see the wood for the trees because Roman could have just added options for each of the pinentry slave ports to the already existing gnupg options menu in his PR instead. I would like that better than a runtime dependency on an option-ifyed pinentry port, but not by much, because the main reason why I never added a runtime dependency on any pinentry to the gnupg port (back when it was still gnupg-devel) still remains: Whatever pinentry you depend on by default through whatever indirection, it will be always be the wrong one for the package users out there. That is why the pkg-message in gnupg exists. So, do what you reckon is best, but I do not think that security/pinentry needs to be changed. Cheers, --=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --------------enigA91514826DBD862CA6A840CE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG3UbwXhc68WspdLARAgfAAJ43LJpZSrZtvBmU9yI9tDXCzfyysQCdEXpo 3BJ1kzy96ICZobDM/rl4qLI= =xygg -----END PGP SIGNATURE----- --------------enigA91514826DBD862CA6A840CE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46DD46EB.2020605>