Package Details: mpv-git 43170.g304d9d5-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: GPL3
Conflicts: mpv
Provides: mpv
Submitter: rpolzer
Maintainer: qmega
Last Packager: qmega
Votes: 149
Popularity: 2.818091
First Submitted: 2012-12-04 09:21
Last Updated: 2016-04-28 01:21

Required by (43)

Sources (2)

Latest Comments

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.

CounterPillow commented on 2016-04-24 17:22

Did bash completion break for anybody else? Because it did break for me.

severach commented on 2016-02-09 08:17

I update my git packages on each version change so that git users get updated no less often than non git users. Updates on each commit seem excessive.

qmega commented on 2016-02-03 06:38

Well, mpv is committed to almost every day. Mirroring every upstream commit might be feasible for some (small / rarely-updating) packages, but for this one it'd be ridiculous.

You could script your upgrade process to explicitly upgrade this package (and similar ones) every time, or after a certain time has passed since your last rebuild. If you want to get fancy, you could even e.g. check https://api.github.com/repos/mpv-player/mpv/commits?per_page=1 and compare the sha with the version of your installed package.

mnovick1988 commented on 2016-02-03 05:26

@qmega: no, just laziness. aur-helpers are tracking version changes, so it automatically flags to update on change.

I really hate having to go through and find whats updated and whats not. Ive gave the same suggestion to alot of maintainers.

qmega commented on 2016-02-03 02:50

@1ace: That shouldn't be necessary. If you have wayland installed at build time, it should automatically be detected and linked against. Is that not working for you?

@mnovick1988: I'll add the ARM stuff momentarily. As for the git thing, I'm a little confused about what you're suggesting. Are you saying I should commit to this package every time there's a commit to mpv upstream? I'm definitely not going to do that. I could maybe be convinced to commit here when there's a release upstream, but given that mpv's releases are basically arbitrary git snapshots, there still wouldn't be a whole lot of meaning to that, IMO. But if you meant something else, please clarify.

mnovick1988 commented on 2016-02-03 00:29

@WorMzy: While i realize this, a bit of automation makes life alot easier. - Although, i could just set up a cron for that though... but im lazy.
Lack of correct term at that moment.(aur helper)

Request: can you add arch=('i686' 'x86_64' 'armv6h' 'armv7h') to the pkgbuild.

1ace commented on 2016-02-02 23:14

Would you be OK with adding `--enable-wayland` ?

WorMzy commented on 2016-01-26 10:17

...no. Users with AUR helpers should understand that this is a -git package and they should upgrade it frequently (or track the upstream repository for changes). The PKGBUILD should only be updated if the dependencies change or the build/package/etc functions need updating.

Also, tools like yaourt are not package managers, they are AUR helpers.

All comments