proposal: merge waf build of s4 to master

[Stefan (metze) Metzmacher]

Hi Volker,

>> Would the proposal to have autogen.sh check if python is available,
>> and offer to download and install it within the Samba build tree be an
>> acceptable solution?
> 
> Not to me, sorry.
> 
>> Or would you happy for us instead have a dual set of tarballs:
>>
>>       samba-x.y.tar.gz
>> and   samba-x.y-with-python.tar.gz ?
> 
>> Perhaps that would address your concerns?
> 
> No, it does not, but my concerns are just what they are:
> *my* concerns. If everybody else in the developer community
> sees the necessity to dump the old build system, I will just
> maintain a separate build system somewhere else for as long
> as I have the energy to do so. It seems I am the only one
> having any concerns at all, everybody else is enthusiastic
> about the new build system. So I am probably just wrong in
> this whole thread.

A few weeks ago we discussed (on #samba-technical), if it would be
possible for waf to dump its configure knowledge to a plain shell based
configure script, which would be able to generate single Makefile.

I assume waf has enough knowledge to to do something like that.
Then we could setup automated tests to make sure this build variant
keeps working.

Would that be a way to address your concerns? If so, I'd try
to code that once Kai reached a stage where we can build source3
with waf.

metze

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100406/cfff0733/attachment.pgp>