group_mapping.ldb and 3.0.25

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Folks,

I'm not prepared to make the commitment to ldb only
for group_mapping.tdb in 3.0.25.  If we for example,
had a ldbsam module that consolidated user and
group accounts and could replace tdbsam and
ldapsam, then it would be an easier decision.  Releasing
group_mapping.ldb would commit us to a path that
I'm not convinced that would be best for production
releases right now (the commitment to a group_mapping
ldb implementation, not ldb per say).  This is not a
statement about ldb in any way.   I just do not want
to use an elephant gun to kill a fly.

In an effort to still the flames over this decision,
neither will I include the original patch to
provide mutli index support in tdb.  We'll limp along
with the performance issues we previously had.

The ldb code should of course stay in SAMBA_3_0, but I
am reverting group_mapping to use the tdb API in order
to make it easier to swap between the two branches for
now.






cheers, jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF2bPIIR7qMdg1EfYRApa8AJ9Vobx9Lbs0X8nMVcHlQcph7p2qQQCgt1KJ
igdIZIC6nozNjQ5o/2oBc68=
=UBPa
-----END PGP SIGNATURE-----