Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - mpv-git

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: mpv-git 43403.g5700da4-1

Git Clone URL: https://aur-dev.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: 161
Popularity: 1.235312
First Submitted: 2012-12-04 09:21
Last Updated: 2016-06-16 04:15

Required by (57)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

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.

mnovick1988 commented on 2016-01-26 08:54

@qmega - no no, its working fine on my end. Im quite satisfied. Once i realized it was auto-detecting ffmpeg-git(which i was using at the previous time-of-build) as the ffmpeg provider, then setting a depend. on it. All was good, i just now always rebuild mpv right after ever ffmpeg build.

**Note: you should bump the git-version per commit. That way package managers with aur support(such as yaourt) can auto-detect the update and treat it as a upgraded package.

qmega commented on 2016-01-13 00:18

@ttz: 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.

@mnovick1988: ffmpeg is the only dependency that is hardcoded in the PKGBUILD because it's the only thing that mpv can't be built without. Since ffmpeg-git provides ffmpeg, it satisfies any pre-checking done by an AUR helper or whatever. When packaging, though, the dependencies are filled based on what the built binary links against. In your case, the package that owns the relevant library files is ffmpeg-git, so that's the package that goes in. When one package provides another, the script has no way of knowing if the thing mpv links against is part of the shared feature set or something that only the special version has. I suppose a special case could be added for ffmpeg, but I'm not sure if that would even be correct. (Would your mpv binary actually still work if you replaced your git ffmpeg with release?) Was this just a curiosity, or is it actually causing problems for you?

mnovick1988 commented on 2016-01-12 20:49

strangely, this sets a dependancy on ffmpeg-git, in the package afterbuilding. but the pkgbuild specifically states ffmpeg is the depend.

ttz commented on 2016-01-10 04:24

suggestion: add lua and luajit as opt deps (needed for On Screen Controller)?

qmega commented on 2016-01-09 23:52

Done. I was thinking about doing that when the change was first made upstream, but got busy and forgot.

This means the binaries built by this package by default must be distributed under GPL3. I don't think this should cause any problems for anyone, but someone please correct me if I'm wrong.