[Pkg-openldap-devel] Request For Comments: SASL transition and OpenLDAP

[Steve Langasek]

On Sat, Oct 21, 2006 at 06:53:52PM +0300, Fabian Fagerholm wrote:

> As you may have read on debian-devel [0], the Debian Cyrus SASL Team [1]
> is working on an improved Cyrus SASL package with the new upstream
> version. During the last few weeks, our pace has increased and there is
> a strong desire within the team to push for inclusion in etch.

> [0] http://lists.debian.org/debian-devel/2006/10/msg00664.html
> [1] http://pkg-cyrus-sasl2.alioth.debian.org/

> The new Cyrus SASL version (2.1.22) includes code to fetch
> authentication data directly from an LDAP catalogue without using the
> in-between saslauthd daemon. In practise, this means we need to
> build-depend on OpenLDAP. However, OpenLDAP depends on SASL, creating a
> chicken-and-egg problem which requires some careful planning to sort
> out. It inevitably involves the OpenLDAP Team.

> The basic plan is as follows:
>      1. The Cyrus SASL Team uploads a version of cyrus-sasl-2.1 with
>         LDAP support disabled. This package will replace the old SASL
>         package.

Why is this necessary now that the symbol versioning problem is fixed?

> Technical details are not the primary question at this point, as they are
> part of the transition work, but we can certainly discuss them if you feel
> it is necessary.

They are *my* primary question, because I don't believe there should be any
transition here at all.  (And if it does involve a transition for some
reason I haven't grasped, it's not likely to be approved for etch.)

Wearing the LDAP hat :),
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/