Package Details: mpv-git 0.37.0_114_g17be6e1990-1

Git Clone URL: https://aur.archlinux.org/mpv-git.git (read-only, click to copy)
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: libmpv.so, mpv
Submitter: rpolzer
Maintainer: qmega
Last Packager: qmega
Votes: 226
Popularity: 0.33
First Submitted: 2012-12-04 09:21 (UTC)
Last Updated: 2023-12-20 08:54 (UTC)

Required by (381)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 37 Next › Last »

qmega commented on 2016-12-01 03:43 (UTC)

@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 (UTC)

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

qmega commented on 2016-06-16 04:22 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

severach commented on 2016-02-09 08:17 (UTC)

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 (UTC)

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.

EndlessEden commented on 2016-02-03 05:26 (UTC)

@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 (UTC)

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

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 37 Next › Last »