Introduction
FTP Team decided it is not allowed to ship waf "binary" as-is into source tarballs available in main component of the archive.
waf "binary" is basically a Python script with an embedded bzip2 tarball unpacked at runtime. A more detailed explanation about it is available here.
How to unpack waf
Here is a quick-and-dirty recipe to generate a unpacked waf instance in your source tarball:
./waf --help &> /dev/null mv .waf-*/waflib waflib sed -i '/^#==>$/,$d' waf rmdir .waf-*
Also, you will need to remove generated .pyc files during clean phase:
find waflib -name "*.pyc" -delete
