mpv-git: Update to 20241213 using Github Releases #14574
Conversation
|
/verify edit: (is the process automatic now, or is this still necessary for every PR?) |
|
All changes look good. Wait for review from human collaborators. mpv-git
|
1 similar comment
|
All changes look good. Wait for review from human collaborators. mpv-git
|
|
ok, so a day after I open this, builds start uploading to Sourceforge again. I guess it up for debate whether this change so be made for the sake of being consistent with mpv.io links and as a more direct source, as opposed to the sourceforge mirror. |
@jack-mil I think GitHub is a better source for binaries, but it's up to you. Please let us know. There's also a conflict on this PR that needs to be addressed. Thanks for your submission. |
The previous Sourceforge mirror has not been receiving recent builds by shinchiro. This commit update the checkver source to use the Github releases API source. All the MPV build are built through Github Actions and automatically released nightly. This is a more direct source than downloading from Sourceforge.
|
Fixed conflict (until the next nightly update at least) and all good from me to use this source (see originial reasoning).
Failing format check is not mine, due to different manifest error on master ( |
|
/verify |
|
All changes look good. Wait for review from human collaborators. mpv-git
|
The previous Sourceforge mirror has not been receiving recent builds by shinchiro. This PR updates the checkver source to use the Github releases API source. All the MPV builds are done with Github Actions and automatically released nightly. This is a more direct source than downloading from Sourceforge.
The build repository https://github.com/shinchiro/mpv-winbuild-cmake/
The repo is directly linked to on https://mpv.io/installation/ as a source of Windows binaries. They are no-longer linking to Sourceforge.
Further updates could be made to modernize this manifest, e.g. #11123
It is also unclear if the change in #9662 of adding the mpv(-git) install directory to PATH is still necessary in 202[45].
I personally dislike it and prefer not to pollute PATH, but I also don't use the package that caused the original issue in #9662.
I have left that as is for this PR.
It is likely that the
mpv.json(non-git builds) will need to be migrated from Sourceforge as well, however there has yet to be a full MPV release since the current v0.39.0, so we have yet to see where the next version will be released (Github releases or Sourceforge mirror).