Re: The waf problem (running nondeterministic binary blobs at build)

Alex Griffin skribis: > Debian replaces all binary 'waf' files with their own > 'waf-uncompressed'. I think our python-waf package should be altered to > produce an uncompressed version, then the waf-build-system should > automatically use that (look at the python-pycairo package for an > example

Re: The waf problem (running nondeterministic binary blobs at build)

Debian replaces all binary 'waf' files with their own 'waf-uncompressed'. I think our python-waf package should be altered to produce an uncompressed version, then the waf-build-system should automatically use that (look at the python-pycairo package for an example of using the system's waf version

Re: The waf problem (running nondeterministic binary blobs at build)

Hi! ra...@openmailbox.org skribis: > I think there is a danger in packaging programs that use the 'waf' > build system. That may pass a regular source code audit. > > If you look at the last line of a waf file you may see strange text > like this: > > #==> > #BZh91AY&Ha

The waf problem (running nondeterministic binary blobs at build)

Hello I think there is a danger in packaging programs that use the 'waf' build system. That may pass a regular source code audit. If you look at the last line of a waf file you may see strange text like this: #==> #BZh91AY&Ha