Hi everyone, in bug #54310 it came out that it doesn't seem to be a good solution to just install heimdal's includes into /usr/include/heimdal and no longer care about them. I guess this decision was founded on the idea to have heimdal and mit-krb5 installed together on one machine (which definitely doesn't work as we know now. ;o) Apart from that, the configure scripts of many packages (like cyrus-sasl) expect to find either gssapi.h or gssapi/gssapi.h in one of the standard include paths. The following symlinks correct these problems and don't seem to hurt in any way. /usr/include/gssapi -> /usr/include/heimdal /usr/include/krb5-types.h -> /usr/include/heimdal/krb5-types.h In addition it would be nice to have InitV style startup scripts for kdc, kadmind and kpasswdd. The patch I attached does two things: 1. Change the ebuild to create the above mentioned symlinks in the src_install section 2. Add the init-scripts heimdal-kdc heimdal-kadmind heimdal-kpasswdd to ${FILESDIR} and change the ebuild to doexe them into /etc/init.d during src_install It can be applied for testing like that: # mkdir -p ${PORTDIR_OVERLAY}/app-crypt # cp -a /usr/portage/app-crypt/heimdal ${PORTDIR_OVERLAY}/app-crypt # cd ${PORTDIR_OVERLAY}/app-crypt/heimdal/ # patch -p1 < /path/to/heimdal-0.6.2-includes+initscripts.patch I would be glad to have some feedback on this. Is there a chance to get that into CVS? Thanks in advance, Torsten
Created attachment 33563 [details, diff] The patch as mentioned above
Thanks for the patch. I agree this should be in portage. Aliz: Do you think making the symlinks will break any other packages? The current ebuild appears to already block if virtual/krb5 is already merged, so that should be alright. Thoughts?
I don't see any problems with the symlink. However imo configure scripts should use krb5-config to get the path to the include dirs.
*** Bug 53540 has been marked as a duplicate of this bug. ***
I have committed all the patches for this bug to -r1.ebuild. Can everyone please test the patches.
I'm testing the patches with the modification mentioned in <a href="http://bugs.gentoo.org/show_bug.cgi?id=58799">bug#58799</a> Shouldn't this ebuild provide also some sample configuration files?
GSSAPI support is built correctly, but kerberos5 mechanism is not available in saslauthd. In order to be built, saslauthd needs to find krb5.h in /usr/include. The heimdal krb5.h has nested includes, so I had to make a few symbolic links in addition to those included in this patch. I list them here (they all link to a file in heimdal/ subdirectory): /usr/include/krb5.h /usr/include/krb5-types.h /usr/include/asn1_err.h /usr/include/krb5_asn1.h /usr/include/krb5_err.h /usr/include/heim_err.h /usr/include/k524_err.h /usr/include/krb5-protos.h I will include the corrected ebuild in bug#58799.
in 0.6.3
closign this time.