[RFC] Get rid of --enable-merged ?

[Andrew Bartlett]

On Tue, 2010-04-27 at 18:13 +0200, Guenther Deschner wrote:
> Hi Jelmer,
> 
> On Thu, Apr 22, 2010 at 01:58:30PM +0100, Jelmer Vernooij wrote:
> > The merged build that we introduced as part of the Franky effort was an
> > interesting idea but I wonder if we should get rid of it. 
> 
> No, no way. The broken and ugly it is sometimes, the current way of how
> test driven development and all work on the merged/shared codebase in
> Samba is going, we (or at least I) *absolutely* need the ability to build
> smbtorture4 right from source3.

Perhaps we could add a make rule that runs waf in Samba4 and produces a
static smbtorture4 binary?

> Once we have a better replacement using waf around, we can get rid of it,
> I think. If someone really is too annoyed by it being enabled by default
> for all devel builds, we can disable it by default maybe.

That's not the annoyance that lead this discussion.  The Samba4 make
based build is bit-rotting really fast, and the only thing that has any
hope of passing 'make test' any more is the waf based build.  By
de-coupling it from Samba3 would mean we are not putting pressure on the
Samba3 build system to change faster than folks are comfortable with. 

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Cisco Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100428/46479bf9/attachment.pgp>