On Mon, Sep 9, 2013 at 7:57 PM, SpinFlo <sl1pkn07@gmail.com> wrote:
Er. No. Mpv-player-git uses different repository than mpv-player-git. And the community mpv use dynamic library (ffmpeg and libass). mpv-build-git use exactly method to build this program. But uses latest updates from ffmpeg and others.. And uses the real method to get real version of the program (version.sh) El 09/09/2013 19:49, "Maxime Gauduin" <alucryd@gmail.com> escribió:
On Mon, Sep 9, 2013 at 6:37 PM, Rob Til Freedmen < rob.til.freedman@gmail.com
wrote:
I'm glad mpv-build-git survived this somewhat obsessive elimination of 'extremely specialized' PKGBUILD's from the AUR.
I wouldn't have any objection of merging mpv-player-git with mpv-build-git - they are both build via mpv-build.git recommended by the developers.
But mpv-git uses a completely different build.
BTW, merging a seemingly 'unused' package without votes and completely unrelated comments doesn't make sense either.
On Sun, Sep 8, 2013 at 1:23 AM, Maxime Gauduin <alucryd@gmail.com> wrote:
On Sat, Sep 7, 2013 at 8:51 PM, Jesse Juhani Jaara < jesse.jaara@gmail.com
wrote:
la, 2013-09-07 kello 20:31 +0200, Karol Blazewicz kirjoitti:
The PKGBUILD file is here https://aur.archlinux.org/packages/mp/mpv-build-git/PKGBUILDbut I think the install file is gone.
http://pkgbuild.com/git/aur-mirror.git/tree/mpv-build-git everything is in there
Apologies for removing this one, I was too hasty and should have checked beforehand whether it was using another repo.
-- Maxime
For the record, mpv devs 'recommend' using these scripts because, and I quote, "distribution packages are often too old or too broken". Our packages are neither old nor broken, those script are absolutely not needed to build mpv on Arch, mpv in [community] and mpv-git in AUR are proofs of that. Even then, using git versions of ffmpeg, fribidi and libass and build mpv-git would have the exact same effect as building mpv-build-git.
-- Maxime
It seems you didn't get my point, and I don't know what point you're trying to make. As I already pointed out, dynamically linking against git versions of said packages is the same as building against locally built versions of those git packages, except it is kinda stupid because you need to rebuild everything everytime you want to update mpv, not to mention saving space and CPU cycles, but those are your calls... As for the "real version", all it would take would be a comment on mpv-git asking the maintainer to use git describe (which is exactly what version.sh is doing) instead of what he's currently using. -- Maxime