[129459] trunk/dports/multimedia/mpv

[Ryan Schmidt]

On Dec 13, 2014, at 7:49 AM, ionic at macports.org wrote:

> Revision
> 129459
> Author
> ionic at macports.org
> Date
> 2014-12-13 05:49:48 -0800 (Sat, 13 Dec 2014)
> Log Message
> 
> mpv: update to 0.7.1. Apply 10.6 patches cleanly against changes base.

> --- trunk/dports/multimedia/mpv/Portfile	2014-12-13 13:23:35 UTC (rev 129458)
> +++ trunk/dports/multimedia/mpv/Portfile	2014-12-13 13:49:48 UTC (rev 129459)
> @@ -6,7 +6,7 @@
>  PortGroup               waf 1.0

> +# Current waf doesn't support --nocache anymore. Set by PortGroup.
> +configure.args-delete   --nocache

Sounds like the waf 1.0 portgroup should be modified then.

I couldn't find a port called "waf". Am I correct in assuming that, like "configure", "waf" is a program that is included in its entirety in software that uses it? If so, then the waf portgroup may need a way to select whether it should deal with "old waf" or "new waf". Or maybe there is a better way to distinguish this, perhaps by automatically detecting whether the version of waf supports this flag.

Actually it looks like mpv does not include a copy of waf, but rather its bootstrap.py script, which is run in a pre-configure block, actually downloads a specific version of it from a server. Ports should not download things other than in the fetch phase. Could this be fixed, please? Add the correct version of waf to the port's distfiles, extract it into the correct place?