On 24/02/07, Joachim Schipper <[EMAIL PROTECTED]> wrote:
On Fri, Feb 23, 2007 at 05:02:08PM -0600, Ryan Corder wrote:
> On Fri, 2007-02-23 at 23:06 +0100, Joachim Schipper wrote:
> > I did not find any evidence of it ever being in ports - it was not under
> > ports/security/*sasl*, at any rate.
>
> sorry, a hasty search on my part. I found a few vague references to GNU
> SASL being in ports in OpenBSD 3.0 and 3.1 from Google led me to believe
> that it was actually true.
>
> on another note, I've been able to tweak the configure script with GNU
> SASL to run successfully under 4.0. I'll mess with the Makefile as well
> to see if it will work.
>
> one change I had to make is that the configure script requires
> krb5-config, so I had to grab that out of /usr/src/kerberosV/src/tools/
> and stick it in /usr/local/bin. I don't know if there is a reason that
> krb-config isn't installed by default, but it seemd to please GNU SASL
> configure script enough.
If you can get this into a usable state, you may want to send in a port
as soon as the port tree unlocks (i.e., around the time 4.1 is
released).
You will, however, want to change configure.in to work without
krb5-config if you do that.
You could look how x11/kde/libs3 deals with it, as it has
ports/x11/kde/libs3/files/krb5-config to go around it.
Joachim
--
viq
