Bug 22583 – Balsa ebuild modification for to add gpgme support

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Chris Irwin 2003-06-10 17:55:39 UTC]

Balsa 2.0.10 and 2.0.11 ebuilds do not use the 'crypt' flag to enable gpg
support (present since balsa 2.0.10).

Reproducible: Always
Steps to Reproduce:
1.USE="crypt" emerge balsa
2.
3.

Actual Results:  
No gpg options present

Expected Results:  
gpg support

Here is a diff against balsa-2.0.11.ebuild proposed for inclusion in a revised
ebuild. (this is tested by myself)

Notes: depends on gpgme >=0.3.14, but not does not work with the 0.4.0 series
(gpgme is slotted). Currently this ebuild depends on 0.3.14 explicitly, until
somebody has a better idea of how to handle the dependancy problem better.

--- /usr/portage/net-mail/balsa/balsa-2.0.11.ebuild     2003-05-15
18:50:24.000000000 -0400
+++ /usr/local/portage/net-mail/balsa/balsa-2.0.11.ebuild       2003-06-10
20:40:04.000000000 -0400
@@ -4,7 +4,7 @@
  
 inherit gnome2 eutils
  
-IUSE="ssl gtkhtml perl ldap"
+IUSE="ssl gtkhtml perl ldap crypt"
 DESCRIPTION="Email client for GNOME"
 SRC_URI="http://balsa.gnome.org/${P}.tar.bz2"
 HOMEPAGE="http://balsa.gnome.org"
@@ -26,7 +26,8 @@
        ssl? ( dev-libs/openssl )
        perl? ( >=dev-libs/libpcre-3.4 )
        gtkhtml? ( >=gnome-extra/libgtkhtml-2 )
-       ldap? ( net-nds/openldap )"
+       ldap? ( net-nds/openldap )
+       crypt? ( =app-crypt/gpgme-0.3.14 )"
  
 DEPEND="dev-util/pkgconfig
        >=app-text/scrollkeeper-0.1.4
@@ -47,6 +48,9 @@
        use ldap \
                && myconf="${myconf} --enable-ldap" \
                || myconf="${myconf} --disable-ldap"
+       use crypt \
+               && myconf="${myconf} --with-gpgme" \
+               || myconf="${myconf} --without-gpgme"
  
        libmutt/configure \
                --prefix=/usr \

[Comment 1 Chris Irwin 2003-06-10 17:58:28 UTC]

Created attachment 13081 [details, diff]
diff to add gpg support to balsa

Original proposed patch submitted as file attatchment (no option while creating
bug report)

[Comment 2 foser (RETIRED) 2003-06-11 04:57:52 UTC]

i was aware of the pgp functionality, but because it isn't currently considered stable by the balsa team i didn't add it. Maybe next release ?

[Comment 3 Chris Irwin 2003-06-11 08:43:36 UTC]

I know it's not considered stable, but maybe it could make it into ~x86?

I have been using since 2.0.10, and it works as well as enigmail for mozilla to my experience.

[Comment 4 foser (RETIRED) 2003-06-11 09:15:07 UTC]

well, common misconception is that ~arch is for unstable stuff. It is not. It is meant for testing ebuilds of stable released packages (or what we consider stable), but i guess i could turn it on in .11 if you can confirm it works correctly and without any problems there (lacking insignificant functionality i do not consider a problem).

[Comment 5 Chris Irwin 2003-06-12 22:36:50 UTC]

well my point is that gpg is included in the stable balsa releases, and testing could begin in the ~x86 arch.

To test I sent some signed and encrypted mails back and forth with a Mozilla -mail user and a Pine user. Mozilla -mail 1.3 w/enigmail worked as expected. Pine couldn't use pgp in mime mode, but this is the fault of the pine pgp plugin I believe, but it did work using the "old openpgp" mode rather than mime. I used default balsa configuration for gpg support (uses mime, and it enables "format = flowed" when selected to sign message.)

Should you wish to test further, my public key is on pgp.mit.edu

[Comment 6 foser (RETIRED) 2003-06-13 03:35:05 UTC]

well, there are no unstable balsa releases, but there are unstable features. pgp support isn't defaulting to being enabled if possible.

Problem is that i know very little balsa users and if i want to guarantee stability i need to go by 'factory defaults' as much as possible. I think i'll try and find the devs and ask them what they think.