Bug 50681 – app-crypt/gpgme: add smime USE flag for S/MIME dependency

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Malte S. Stretz 2004-05-10 15:29:57 UTC]

GpgME can be built with and without S/MIME support. To get it, it needs to find the gpgsm tool around which is part of app-crypt/newpg. I suggest a new USE flag "smime" to enable the S/MIME stuff. I'll attach a patch against the gpgme-0.4.0.ebuild.

Reproducible: Always
Steps to Reproduce:

[Comment 1 Malte S. Stretz 2004-05-10 15:32:05 UTC]

Created attachment 31129 [details, diff]
Patch against gpgme-0.4.0.ebuild.

Note that there is bug 31745 and bug 49608 for newer versions of gpgme which
might need some more modifications.

[Comment 2 Richard Fujimoto 2004-06-23 16:21:34 UTC]

Shouldn't the ebuild also enable smime in the econf line?  Something like this?

src_compile() {
    use smime && myconf="--with-gpgsm=`which gpgsm`" || myconf="--without-gpgsm"
    econf\
        ${myconf} \
        $(use_enable nls) \
        $(use_enable crypt gpgmeplug) \
        $(use_enable doc maintainer-mode) || die "econf failed"
    emake || die
}

[Comment 3 SpanKY 2004-07-23 23:22:25 UTC]

added to 0.4.7

[Comment 4 Gregorio Guidi (RETIRED) 2004-07-28 07:04:09 UTC]

May I ask that this bug be reopened?

First, smime should be listed in use.local.desc,
and most importantly, the smime flag is currently useless,
as the 'gpgsm' binary is now provided in the development
version of gnupg (1.9.x), currently hardmasked and not going
to be unmasked soon (bug 37109). However, without the mask on gnupg
the ebuild should be something like:

	DEPEND="...
		!smime? ( >=app-crypt/gnupg-1.2 )
		smime? ( >=app-crypt/gnupg-1.9 )
		...

	...
	use smime && myconf="--with-gpgsm=gpgsm" || myconf="--without-gpgsm"
	...