From my experience, most sites using zephyr use kerberized-zephyr. This makes the zephyr support in the gaim packages a little lacking, since gaim has to be rebuilt to use the kerberized zephyr support (as opposed to the un-kerberized zephyr support built now). Since Fedora ships with kerberos, all that's required is adding '--with-krb4' to the configure line, and a BuildRequires of krb5-devel.
Having the Gaim RPM depend on kerberos doesn't seem like a great idea to me... Having a separate gaim-zephyr RPM containing the zephyr plugin compiled with kerberos support sounds like a good idea. warren: If you're interested, the gaim.spec Gaim CVS does something very similar to this for the silc protocol. I'm not sure how I feel about changing the upstream gaim.spec to build zephyr as a separate RPM and/or with kerberos support.
Fedora at least already requires kerberos libraries for core components of our operating system, so it is already present and installed for users who use our gaim. I dislike the idea of sub-packages for protocols that other people include, so I am considering enabling kerberos in our gaim. This of course is not a good change for upstream gaim.spec. This sound ok?
So, I don't doubt that you are correct that important parts of fedora depend on kerberos ... but nothing on my system depends on either krb5-devel or the kerberos libraries themselves. openssl-devel does have a transitive dependency on krb5-libs, but there are any number of systems which might not require openssl-devel. That said, I won't cry if the Fedora gaim package depends on kerberos. Ethan
Wow, I hadn't realized so many things depend on kerberos. xine? grip? wget? xscreensaver? Funky. I don't have any problems with the Fedora RPM being built with a kerberized-zephyr.