[129459] trunk/dports/multimedia/mpv

[Ryan Schmidt]

On Dec 13, 2014, at 3:29 PM, Mihai Moldovan wrote:
> 
> On 13.12.2014 08:16 PM, Ryan Schmidt wrote:
>>> +# 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.
> 
> The problem at hand is that waf is being most likely downloaded with an
> unspecific version ("current") by I guess most software. I refrained from
> changing the PortGroup to not break other ports utilizing waf.


>> 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?
> 
> I should probably inline that. Find a way to fetch a specific version, too. Will
> look into that.

mpv, at least, currently fetches exactly 1.8.1.

If any port fetches "latest version" that should be fixed as well, because that results in non-repeatability.