Version bump of gpgme
Created attachment 3174 [details] gpgme-0.3.8.ebuild gpgme-0.3.8.ebuild, just a version number bump, but also requires gnupg >= 1.0.7.
Created attachment 3175 [details] ChangeLog ChangeLog
Created attachment 3264 [details] gpgme-0.3.9.ebuild New release: version bump, myconf changes for use vars, see ChangeLog
Created attachment 3265 [details] ChangeLog (0.3.9) ChangeLog for gpgme-0.3.9
Created attachment 3277 [details] gpgme-0.3.9.ebuild Updated for crypt? gpgsm, use instead of previous 0.3.9
Created attachment 3278 [details] ChangeLog (new 0.3.9) modified to reflect new 0.3.9 with use crypt dep
gpgme can also use pth like gpgsm (bug 6850), so I guess I'm proposing a 'threads' use variable so pth can be in the deps.
Seemant stuck gpgme-0.3.9 in Portage while I was gone. Did it include all the features that you requested in this bug?
I guess --enable-maintainer-mode isn't necessary for the info docs, even though the readme says it is. It doesn't have crypt? gpgsm dependency, but gpgsm isn't in portage yet either. Also, I think a 'thread' use variable would be good so that gpgme (and gpgsm) could be built with pth, which seems to be a good thing. But since those two options are not available right now, the gpgme-0.3.9 in portage looks fine to me. When (if) gpgsm is put in portage, then it could go to gpgme-0.3.9-r1 with a crypt dep.
Also, I had the gpgmeplug enabled only for use crypt, but it's your call.
gpgme-0.3.10 is out. Has a VERSION doc. Also, I still think gpgmeplug should only be enabled with use crypt. Works fine just copying 0.3.9 ebuild. What about the tests? I think there should be some use var that would put these in /usr/share/gpgme.
gpgme is now at 0.3.12, and has also been branched to 0.4, but those are unstable. Current ebuilds can probably just be version bumped, but there might be some features missing.
Commited. I commented out the gpgms dependency since gpgms isn't available in portage.
