openldap-sasl-client ports

[Xin LI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/27/11 13:44, Yuri Pankov wrote:
> Hi,
> 
> Looks like dependency recording for openldap2{3,4}-sasl-client ports is
> broken again (I tried to fix it in ports/135664). I can take a look at

How do I reproduce this?  (so I would be able to test before commit? Or
it's someone else broken it?)

> fixing it again, but the real question here is - do we really need them
> now, when options are the same for -client and -server ports?

I'm not sure if I understood what you mean -- do you mean that now that
we have OPTIONS menu for both -client ports?

Speaking about the two different ports, I believe the real reason for
having both is to make it easier to install binary packages (we build at
FreeBSD cluster).  Note that we have no preconfigured ports that uses
them though.

I do not personally use SASL'ed OpenLDAP but I am not really sure if
it's Okay to just axe the package...

Cheers,
- -- 
Xin LI <delphij at delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!	       Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iQEcBAEBCAAGBQJNQfexAAoJEATO+BI/yjfB+1IIAJuIU5F9hhTPUY+Im0+JwGip
LshjR4l2sM/Mx31xhgMv3rC8MVP3+yjvM4M49+dKSK3XwZmDVf9TM8R7OJ86dVuJ
kVcIqkX5JMDm/3sv+TfIH31jFhuOf7foiVd5g86p+Ll81RAh6QoLTl1zYiCaRo6p
CJfuU/t5d1sZ7iMk245vP9ueOWiuf66OwdPyxJ8C6D8Ux0jqAJPLmZXpKFCiqQk/
KSei8wp/KfC7Yxgf94xVc+smKOsLllFBv+RezNZ97CusYBhVHmBd0UMKmg/RHrrv
Knop881BsgFFmgu3bfzZcndnTbfUfXZda5h1hHo2lpns6gWEUheq5Jh1vGKdkno=
=pbte
-----END PGP SIGNATURE-----