Stuart Henderson, 22 Nov 2014 14:53: > I have to say, I'm very un-keen on using this self-extracting waf > distribution with no easy way to look at the contents, it isn't > something we should be encouraging in ports.
all the waf versions have checksums on their official site and the mpv 'bootstrap' script (basically a glorified downloader) checks it as well. incidentally, mpv has moved on to a newer waf version: https://github.com/mpv-player/mpv/blob/master/bootstrap.py -WAF = waf-1.7.16 +WAF = waf-1.8.1 the normal waf usage pattern (according to the docs) is embedding a certain waf version executable (it is one single python script that extracts additional files upon execution) and distribute it with the particular software that uses it for building. projects like mpv that refuse to do this make the port uneccessary complicated, but it is essentially the same as having the waf file in ${WRKSRC}. c'est la vie. -f -- forgive your enemies but never forget their names.