> By either of the two solutions, you need to repack the upstream
> source to remove the problematic files, just like what we did with
> other packages to make their source tarball DFSG free.
This waf issue has nothing to do with being DFSG free.
It is a policy question concerning making examining sources more
convenient for people and automated tools.
Doing this
./waf --help &> /dev/null
mv .waf-*/waflib waflib
sed -i '/^#==>$/,$d' waf
rmdir .waf-*
cannot magically change non-free into free.
> And, if you don't want to bother for future releases, persuade and
> help upstream to use another build systems like Automake and CMake.
In the case of minidjvu, the upstream ALREADY DOES use autoconf.
The sources contain a configure.ac file.
Again: the waf file is *not used* in the Debian build.
Which is why I am not so worked up about this issue. It seems to me
that the convenience of examining sources is only an issue for sources
that are actually used.
--Barak.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
