Package Details: mpv-git 0.24.0.r189.gdc7d71fc8e-1

Git Clone URL: https://aur.archlinux.org/mpv-git.git (read-only)
Package Base: mpv-git
Description: Video player based on MPlayer/mplayer2 (git version)
Upstream URL: https://mpv.io
Keywords: media player video
Licenses: GPL
Conflicts: mpv
Provides: mpv
Submitter: rpolzer
Maintainer: qmega
Last Packager: qmega
Votes: 167
Popularity: 2.892582
First Submitted: 2012-12-04 09:21
Last Updated: 2017-04-02 01:09

Required by (64)

Sources (2)

Latest Comments

qmega commented on 2017-04-02 00:56

I decided not to switch back at the time because mpv's releases are pretty much arbitrary git snapshots, and mpv built from master identifies itself by a commit, not the last or next version, so I figured a release-based version still wouldn't mean much. Also, the releases aren't tagged on master, but on a separate branch with extra merge + version commits, so the version tag isn't actually reachable from HEAD, and getting the latest tag has always been a little "interesting". (I never really liked just grabbing the latest tag - it wouldn't give you the tag you wanted if e.g. fixes were backported to an old release.)

I don't feel very strongly about this, so I'll reinstate some kind of release-based pkgver for now, but I wonder if a date-based version format would be more appropriate. What you really want to know when you look at the version is how out-of-date it is, right? The date you built it or the date of the last commit would be better indicators of that than release numbers, which for mpv are somewhat arbitrary and irregular. Opinions?

WorMzy commented on 2017-04-01 23:18

This package used to use a similar pkgver (see https://aur.archlinux.org/cgit/aur.git/commit/?h=mpv-git&id=9643c547576c6036bea0c01799d1dc5a5bb0c67f ), but was removed because upstream stopped making releases, and the package in community/ switched to commit versioning.

I'd say there's a good argument for switching back to a more descriptive pkgver now.

escondida commented on 2017-04-01 21:37

I'd like to suggest using the following pkgver(), which would provide a more informative version number along the lines of "0.24.0.r189.gdc7d71fc8e", where r189 is revisions since last tag and everything preceding it is the tagged version number.

pkgver() {
cd mpv
tag="$(git tag -l --sort=version:refname | sed -n '$p')"
printf '%s.r%s.g%s' \
$(echo $tag | sed 's/^v//') \
$(git rev-list --count "$tag"..HEAD) $(git rev-parse --short HEAD)
}

qmega commented on 2017-01-07 02:17

Can't reproduce, but based on your error my guess is your python / python-docutils packages are mismatched since the Python 3.6 upgrade, so you're running python 3.6 with docutils in /usr/lib/python3.5 or python 3.5 with docutils in /usr/lib/python3.6. A full system upgrade with up to date mirrors should fix it. If not, check your versions of each package to be sure: latest as of this writing are python 3.6.0-1 and python-docutils 0.13.1-2 (obviously you need both installed, but as they're makedeps I'm assuming you do).

thelongdivider commented on 2017-01-05 06:58

Anyone else having this problem?

Traceback (most recent call last):
File "/usr/bin/rst2man", line 21, in <module>
from docutils.core import publish_cmdline, default_description
ModuleNotFoundError: No module named 'docutils'

Build failed
-> task in 'rst2man' failed (exit status 1):
{task 140156037857856: rst2man mpv.rst -> mpv.1}
' /usr/bin/rst2man --strip-elements-with-class=contents ../DOCS/man/mpv.rst DOCS/man/mpv.1 '
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build mpv-git.

qmega commented on 2016-12-01 03:43

@Soukyuu: That's been asked a couple times before. Here's what I said last time:

(TL;DR: They aren't really optdepends the way the packaging system sees them. Either they were linked against at build time, and mpv won't run without them (hard depend), or they weren't, in which case even if you install them they can't be used unless you rebuild mpv. The situation isn't ideal, and I'm open to ideas.)

An optdepend tells the packaging system that you can freely install or uninstall it and you will just get/lose the associated optional functionality. Although Lua support is an optional dependency for mpv, it doesn't work like that. If you don't have it installed when you build, Lua support won't be there, even if you install Lua later. And if you build with Lua support, uninstalling Lua will render your mpv unable to run. If you have a compatible Lua installed when you build mpv, it will be picked up and will be a hard depend of the generated package (as it should be, because the package won't work without it). As a compromise, the last time this was asked I added a message on install that addresses this issue and specifically mentions Lua, but I have it only on the first install to avoid annoying people.

Here's also what I said last time about the auto-detecting dependencies thing: I know the dependency system is non-ideal, but I haven't thought of anything better. The way it is prevents dependencies from getting out of sync, and allows everyone to use whichever optional features they want without having to install a bunch of stuff they don't or edit the PKGBUILD every time. The price is that you have to figure out which extra packages you need the first time you install, but at least you only have to do that once. If you can think of a better system, I'm all ears.

Soukyuu commented on 2016-11-29 19:41

lua51/luajit are needed for lua/OSC support, maybe you could add them as optional dependencies?

qmega commented on 2016-06-16 04:22

For anyone who uses nnedi3 or superxbr: They're being removed soon (https://github.com/mpv-player/mpv/pull/3236). I've removed the enable flag from this package already because I'll be out of town for a while and don't want the package to break if they remove it while I'm gone.

Both scalers are already implemented as user shaders: https://github.com/bjin/mpv-prescalers
For now you can also just add the flag back to the build if you want, but user shaders will be the way to use nnedi3 or superxbr in the future.

qmega commented on 2016-04-25 03:01

FYI, there's a bash completion for mpv at https://github.com/2ion/mpv-bash-completion which seems pretty well updated. (I use zsh, so I haven't personally used it.) Looks like the bash-completion package has removed their mpv thing for the next release, so you might want to check that out. Or switch to zsh, it's better ;)

CounterPillow commented on 2016-04-24 17:32

Nevermind me, some retard broke /usr/share/bash-completion/completions/mpv, fault isn't in this package.

All comments