[RFC] Switch on tdb2 API by default?

Kai Blin kai at samba.org
Thu Sep 29 12:03:02 MDT 2011

Hash: SHA1

On 2011-09-29 10:42, Jelmer Vernooij wrote:
> On Thu, Sep 29, 2011 at 07:52:48AM -0700, Kai Blin wrote:
>> On 2011-09-29 02:40, Dan Shearer wrote:
>> It gets a bit more complicated than that, though.
>>> The Python team says "Python runs everywhere". That's their goal. So it
>>> makes sense to me to push autoconf maintenance on weird/horrible
>>> platforms off to the Python team.
>> The Python team did end-of-life python2, though, and Samba doesn't work
>> with python3. This causes all sorts of pain on ArchLinux already, where
>> they are bleeding edge enough to make "python" point to python3 and
>> break our build system.
> ... and going against the recommendations of Python upstream, which
> recommends shipping python 3.0 as "python3" and python 2.x as "python"
> even now that Python 3.X is out.

They quote an in-draft PEP that says "python" can be python3 on bleeding
edge distros. :)

> python 2.x does what we do; upstream probably won't
> do any more feature work on it, but we can expect important bugs to be fixed
> for quite some time. I don't see any reason to switch to Python 3 at this
> point, and make life harder on the large number of platforms that
> don't ship python3.

Right. I didn't bring up python3 here, Dan did, for size comparisons, as
he mentions.  Let's just drop that part of the discussion. We were
talking about waf only vs. waf for AD, autoconf for fileserver only.


- -- 
Kai Blin
Worldforge developer http://www.worldforge.org/
Wine developer http://wiki.winehq.org/KaiBlin
Samba team member http://www.samba.org/samba/team/
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the samba-technical mailing list