[Pkg-openldap-devel] RFC: introducing slapd-contrib binary package

[Ryan Tandy]

Hi Steve,

On Mon, May 5, 2014 at 10:21 PM, Steve Langasek <vorlon at debian.org> wrote:
> On Sun, May 04, 2014 at 09:31:50PM -0700, Ryan Tandy wrote:
>> Assuming such a package were to be added, should smbk5pwd become part of
>> it, or remain in its own package? How about other contrib modules that
>> bring additional Depends? (pw-radius, ??)
>
> Well, bug #358829 is about packaging a library; that certainly doesn't seem
> like it should go in a package with all of the others.

Good point. That's doubly a separate project then, as I haven't tried
packaging a library before. And besides that bug is awfully quiet...
For now I'm talking principally about contrib/slapd-modules/*.

> I don't have any strong opinion on whether contrib plugins should go in one
> package or several.  You could start with a single package and see if anyone
> complains about the extra dependencies.  In that case, maybe it makes sense
> to keep smbk5pwd separate, at least initially.

As long as you're OK with the basic idea of adding a new binary
package, this all makes sense to me.

One other question, about upgrades. I had intended for slapd to
Suggest the new package and not pull it in by default. But if
autogroup and nssov are to move from slapd, then I guess slapd needs
Recommends or Depends on the new one in order to transition users of
those modules? Maybe I should leave those where they are and start
just with the modules that aren't currently packaged.

Thanks for the feedback!