From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Cc: Rutger Helling <rhelling@mykolab.com>
Subject: [rhelling@mykolab.com: 02/02: gnu: mpv: Update to 0.28.0.]
Date: Wed, 27 Dec 2017 14:18:32 -0500 [thread overview]
Message-ID: <20171227191832.GA21118@jasmine.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hi Rutger,
----- Forwarded message from Rutger Helling <rhelling@mykolab.com> -----
Date: Wed, 27 Dec 2017 04:52:26 -0500 (EST)
From: Rutger Helling <rhelling@mykolab.com>
To: guix-commits@gnu.org
Subject: 02/02: gnu: mpv: Update to 0.28.0.
rhelling pushed a commit to branch master
in repository guix.
commit abc5ef5a7f7fecb99ca8213c0962f42cc1a65552
Author: Rutger Helling <rhelling@mykolab.com>
Date: Wed Dec 27 10:46:26 2017 +0100
gnu: mpv: Update to 0.28.0.
* gnu/packages/video.scm (mpv): Update to 0.28.0.
[inputs]: Change ffmpeg to ffmpeg-git, add wayland-protocols.
-----
As a frequent user of mpv, I also noticed that its latest release
requires this unreleased branch of FFmpeg (it will eventually be
released as FFmpeg 3.5).
I wonder, does mpv 0.28.0 bring some new features that make it worth it
to build three copies of FFmpeg? There was already ffmpeg-2.8 and
ffmpeg@3.4.1 (the latest upstream release). And, do we know if this copy
of FFmpeg is ready to be deployed?
If I remember correctly, FFmpeg is pretty expensive to build from
source. But maybe it's no big deal, or the new features are worth it. Or
maybe we should replace ffmpeg@3.4.1 with this unreleased development
branch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-12-27 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 19:18 Leo Famulari [this message]
2017-12-27 19:52 ` [rhelling@mykolab.com: 02/02: gnu: mpv: Update to 0.28.0.] Rutger Helling
2017-12-27 23:20 ` Leo Famulari
2017-12-28 5:50 ` Rutger Helling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171227191832.GA21118@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=rhelling@mykolab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.