[RFC] Switch on tdb2 API by default?

Rusty Russell rusty at rustcorp.com.au
Mon Sep 26 04:16:51 MDT 2011

On Mon, 26 Sep 2011 08:41:17 +0200, Volker Lendecke <Volker.Lendecke at SerNet.DE> wrote:
> On Mon, Sep 26, 2011 at 12:09:23PM +0930, Rusty Russell wrote:
> > On Sat, 24 Sep 2011 11:11:29 +0200, Volker Lendecke <Volker.Lendecke at SerNet.DE> wrote:
> > > On Sat, Sep 24, 2011 at 05:33:59PM +0930, Rusty Russell wrote:
> > > > Sure I'll do it, but it feels wrong and foolish.
> > > 
> > > To you it might. The problem is that the world is larger
> > > than Linux.
> > 
> > Please explain; Python is generally more portable than Samba, perhaps
> > there are specific ports we need?  Or is it waf?
> > 
> > > But for existing S3 uses we need autconf/make to work in the future.
> > 
> > Why?  I think we're allowed to make their binaries smaller and their
> > builds faster.
> > 
> > On the other hand, it'd be nice to clear up some of the tangled #include
> > lines in the s3 source, and make dependencies more explicit.  I'm sure
> > there is other cruft I don't know which could be cleaned too...
> I've been at customer places more than once with just a
> plain proprietary Unix where downloading *anything* was a
> major obstacle. Having to tell the customer "Sorry, we
> first need to compile python" just to compile a current
> Samba version is just not an option for me.

I've been there too, years ago.  Of course, since I needed a compiler
and emacs, I'm not sure adding python would make it worse.  And it'd be
nice to have git.  Plus, without python you can't 'make test'.

But it would far less hassle to automatically provide a source tree of
Samba which includes the entire python source.  I'm happy to do this
as a .tar.Z for you.  We can host it on samba.org.

> If you can't
> make tdb2 work in the autoconf Samba3 build, then it won't
> be in the default install for that release. I would not like
> it, but if it is not possible to make tdb2 work in autoconf,
> then it will be a pure Samba4 thing.

It's possible, but at some point, we have to move on.  I'd rather do
that *before* I have to wade into the autoconf stuff again...


More information about the samba-technical mailing list