We're starting to get packages (such as msmtp) which use gsasl instead of cyrus-sasl as their default sasl library, and it would be nice if we had an ebuild to support it. That said, sasl scares me!
Created attachment 34754 [details] dev-libs/gsasl-0.1.1.ebuild Initial ebuild. Please comment.
Works for me, and msmtp builds against it successfully. At least as far as gsasl is concerned, kerberos seems fine since a kerberos dep is currently the only way to obtain gssapi. (I know almost nothing about kerberos, though, so you may just want to ignore me.) Why do we disable krb4? Heimdal used to be krb4, back when I originally added it to portage, has it moved on to krb5 now? (If so, then I have no problems w/ disabling krb4 support.) I might be missing it, but this ebuild builds libgsasl (the library), but not gsasl (a command-line client). Perhaps we should have both libgsasl and gsasl ebuilds, with the latter depending on the former? In either case I think the deps are right. According to the gsasl docs the dependencies are deliberately minimal because a lot of current gsasl use is in embedded devices. Finally, I suggest net-libs as the place to put the library; I'm not quite sure where to put the client. (Come to think of it, is there any reason that we don't move cyrus-sasl to net-libs?)
Created attachment 34789 [details] net-libs/libgsasl-0.1.1.ebuild ah... I've overlooked the download site. Attached is the libgsasl ebuild. I took out the krb4 because that is the default config in cyrus-sasl. The reason I want to change the USE flag kerberos to gssapi is becuase it is missing leading (correct me). According to gsasl homepage, KERBEROS_V5 is support using GNU Shishi, and GSSAPI is provides by Heimdal, mit-krb5, GNU GSSlib. gsasl ebuild will follow. I don't know where should we put it. net-utils?
Created attachment 34790 [details] gsasl-0.1.1.ebuild net-mail/mailutils can use libgsasl too, but I don't use/know it enough to test it. Please test it if you can. Thanks.
Hmmm, I've never looked at mailutils. Let's go ahead and get gsasl in the tree, and we'll wait on mailutils until somebody asks for gsasl support there. (The basic idea is that the person who knows enough to request it can also test out the results for us.) As for the gsasl client, I don't think we have a net-utils, so I would suggest net-misc. Also, I suspect that gsasl should have a depend of =net-misc/libgsasl-${PV} to keep the lib and client versions in sync.
In CVS.
