Loading...
Request History
llyyr created request
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:19"
staging-bot accepted review
Picked "openSUSE:Factory:Staging:adi:19"
dimstar accepted review
anag+factory accepted review
Staging Project openSUSE:Factory:Staging:adi:19 got accepted.
anag+factory approved review
Staging Project openSUSE:Factory:Staging:adi:19 got accepted.
anag+factory accepted request
Staging Project openSUSE:Factory:Staging:adi:19 got accepted.
What about using this update as an opportunity to remove the
git
revision in the version format? We can follow mpv's own release tags.mpv tags releases once or twice a year, so we will be back to using them again anyway. And mpv release tags are just arbitrarily cut off from the current HEAD. See release cylce part of the readme: https://github.com/mpv-player/mpv?tab=readme-ov-file#release-cycle
The advantage is that we would share the same release schedule of mpv that other distributions follow. As of now the mpv Factory package updated multiple times a year. I am not aware of a plan to go back using tag releases, can you share?
I meant that we'd end up updating to a git rev in a month or two's time anyway, even if I update it to the tarball for this particular update. I'm not sure it's worth the effort of downgrading the package for it
That's why I suggested it for this update, so there would have been no version downgrade.