LDB hitting production state

Bjoern JACKE bjoern at j3e.de
Tue Oct 31 14:01:43 GMT 2006


some days ago I duscussed with metze how to proceed with packaging of
ldb as it is used since a while in samba4wins and it will be used soon
in Samba 3 release. As ldb will provide the ldb tools these tools
would be provided by samba4wins, Samba 3 (and maybe soon by other
projects, too).

To avoid file conflicts of those packages it would be best to create a
stand alone ldb-tools package which samba4wins, samba3 etc. will
depend on then. If ldb-tools will be build out of a samba3 tar ball
the problem would be that there are not all database backends
included. samba4wins for example will require such a backend which is
not in samba3's ldb branch. According to metze these backends can
already be provided as plugins and be loaded on demand.  That's nice
indeed. But: There should be a standard path be defined, where the ldb
modules are being put. IMHO it wouldn't be good if this is under the
samba libdir path as that would be different for samba3 and samba4 for
example. I would suggest to change that default path to /usr/lib/ldb/
soon.  That change would be very good to be made before ldb is getting
into production state in Samba3 release.

Metze, if I forgot something to mention, please correct me.

What do the ldb guys think? Simo, Tridge?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20061031/56fd752c/attachment.bin

More information about the samba-technical mailing list