Date: Sun, 12 Dec 2004 17:09:10 -0800 From: Doug Barton <DougB@DougBarton.net> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: ports-committers@freebsd.org Subject: Re: cvs commit: ports/security/gpgme Makefile pkg-plist ports/security/gpgme/files patch-configure patch-gpgme-engine-gpgsm.c Message-ID: <41BCEBB6.6020406@DougBarton.net> In-Reply-To: <200412121711.31008.michaelnottebrock@gmx.net> References: <200412111328.iBBDS6Eq056365@repoman.freebsd.org> <1102790363.50655.1.camel@shumai.marcuscom.com> <200412112007.28045.michaelnottebrock@gmx.net> <200412121711.31008.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Nottebrock wrote: > On Saturday, 11. December 2004 20:07, Michael Nottebrock wrote: > >>On Saturday, 11. December 2004 19:39, Joe Marcus Clarke wrote: >> >>>Why enable pth support? FreeBSD shouldn't require this, and it just >>>adds another dependency? I had specifically disabled it for that >>>reason. What about making it optional? >> >>The pth support doesn't use pth instead of FreeBSD's native pthread libs, >>it produces an additional library that applications/developers might want >>to use for portability reasons. Making it optional isn't worth it IMO since >>pth is a small package anyway (<200kb) and the option would need to default >>to on in order to make the gpgme-package feature-complete. > > > Update: I've talked to Marcus Brinkmann of gpgme and he tells me the pth > support is, to his knowledge, only used internally g10, so it should be safe > to turn it off at least for now. I'll make it an OPTION with default to off. > This is an excellent resolution to this issue. Thanks for doing the extra detective work. Doug -- If you're never wrong, you're not trying hard enough
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41BCEBB6.6020406>