summarylogtreecommitdiffstats
path: root/PKGBUILD
AgeCommit message (Collapse)Author
2017-11-02build against ffmpeg-mpv-git (now co-installable) by defaultPhilip Sequeira
Building against system ffmpeg is still possible by uncommenting a line in the PKGBUILD. In that case we're now using the new --enable-ffmpeg-upstream flag, so we can drop the patch. While we're in the neighborhood, remove that old samba include stuff. I guess it was needed at some point; pkg-config handles it now.
2017-10-30update ffmpeg workaroundPhilip Sequeira
Can't just revert the commit anymore, as the surrounding code has changed since. Add a patch with a simple workaround that will hopefully not break too often. PR #5033 has been merged(ish) upstream. Remove the patch. mpv now requires git master ffmpeg; the latest release is not new enough. This package probably should start depending on ffmpeg-git, but I'm not switching it yet because that isn't provided by the current ffmpeg-mpv-git package. We'll just live with the _dirty in the version for now. If this goes on, I'll strip it from the pkgver, but it will stay in the built binary as long as it's true, to respect those handling bug reports upstream. Some kind of option to avoid applying the patch when using ffmpeg-mpv should be doable, though, so those who are following upstream's recommendations can get a fully supported build without -dirty.
2017-10-27allow building against upstream ffmpeg for nowPhilip Sequeira
Also apply a patch for the issue that caused this mess. See the comments on the AUR page for some links to what's going on. This is a temporary situation until things settle down. I'm not sure what I'll do if mpv continues to reject upstream ffmpeg long-term, but I probably won't be continuing to carry these patches.
2017-10-15add dependency-setting options for vulkan and shadercPhilip Sequeira
2017-09-13version bump for 0.27.0 releasePhilip Sequeira
I don't really think this is necessary; mpv's releases are pretty arbitrary and users of this package should just update whenever. But bumping isn't any harder than complaining about semantics in the comments when it's flagged so I'll just do it. Not sure if I'll continue to do it in the future.
2017-07-23use mpv's own version script for pkgver()Philip Sequeira
2017-06-23vf-dlopen removedPhilip Sequeira
2017-06-07cplugins no longer disabled by defaultPhilip Sequeira
So we don't need the option.
2017-05-29basic build options systemPhilip Sequeira
2017-04-01reinstate release-based pkgver()Philip Sequeira
With some minor changes. I still don't really like doing it this way... Maybe we'll switch to a date-based version or something in the future.
2016-06-16remove --enable-gpl3 (soon to be removed upstream)Philip Sequeira
The functionality it provides is already possible with user shaders: https://github.com/bjin/mpv-prescalers (I'm doing this now because I'm going out of town soon and don't want the package to break if upstream removes the flag while I'm gone.)
2016-04-27remove dependencies that were only needed for the install filePhilip Sequeira
2016-04-27remove install stuff that is now done by hooksPhilip Sequeira
2016-02-02add armv6h and armv7h architecturesPhilip Sequeira
2016-01-09stop manually installing docsPhilip Sequeira
Some of them are already installed by mpv's own installer, ending up with duplicates. The official package only removed the dups, but I'm just removing all of them and leaving it up to mpv what it wants to install.
2016-01-09enable GPL3Philip Sequeira
2015-08-30get rid of release stuff from pkgverPhilip Sequeira
Releases aren't relevant anymore (at least for now). The new pkgver format matches the official package in community. Hopefully this will reduce confusion.
2015-08-20message on first install about installing optional featuresPhilip Sequeira
Also, use a better (?) way to avoid the false fakeroot dependency, and print detected dependencies when packaging.
2015-06-09dependency detection is stable and the old deps are out of datePhilip Sequeira
2015-06-09inital importPhilip Sequeira