From: Rutger Helling <rhelling@mykolab.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [rhelling@mykolab.com: 02/02: gnu: mpv: Update to 0.28.0.]
Date: Thu, 28 Dec 2017 06:50:12 +0100 [thread overview]
Message-ID: <20171228065012.589e2724@mykolab.com> (raw)
In-Reply-To: <20171227232001.GC2331@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
Hi Leo,
On Wed, 27 Dec 2017 18:20:01 -0500
Leo Famulari <leo@famulari.name> wrote:
> On Wed, Dec 27, 2017 at 08:52:12PM +0100, Rutger Helling wrote:
> > Hi Leo,
> >
> > You can find the new features at:
> > https://github.com/mpv-player/mpv/blob/master/RELEASE_NOTES
> >
> > There are two reasons for me personally why I wanted to update:
> > 1. The mpv developers only support the latest release.
> > 2. The initial Vulkan support, which I've got working (x86_64 only
> > for now). I can't merge it yet until core-updates is merged though.
> >
> > I agree having three ffmpeg versions is undesirable. However,
> > looking at the release notes ("This release needs recent FFmpeg
> > (newer than 3.4) due to major refactoring.") this is hopefully a
> > one-time thing.
> >
> > When stable ffmpeg is updated we can get rid of the -git version.
> > mpv is the only one using the -git version and it's been very solid
> > for me, so I don't foresee problems there. Replacing ffmpeg@3.4.1
> > entirely with this -git version seems too extreme a solution to me.
> >
> > Hopefully that explains my rationale a bit!
>
> Okay, let's keep this mpv and FFmpeg. I'm always eager to update to
> the latest releases of C-language programs that handle untrusted
> input, and it sounds like the mpv team is moving on from mpv 0.27.0.
>
> Personally I think it's bad practice for mpv to depend on some random
> commit of FFmpeg, but that is mpv's choice.
>
I agree, it's an unfortunate situation that hopefully shouldn't take
too long.
> In the future, please send patches that introduce unreleased versions
> of widely used libraries like FFmpeg to guix-patches for review.
>
> The packaging guidelines say, "We usually package only the latest
> version of a given free software project." [0]
>
I'll send a patch in next time first, sorry about any inconvenience.
Hopefully this is a one-time situation though.
> I interpret "latest version" to mean the latest version released in
> the way that the upstream developers typically do their releases. For
> FFmpeg, this is a tarball.
>
> Thank you very much for taking the time to explain your rationale!
>
> [0]
> https://www.gnu.org/software/guix/manual/html_node/Version-Numbers.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-12-28 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 19:18 [rhelling@mykolab.com: 02/02: gnu: mpv: Update to 0.28.0.] Leo Famulari
2017-12-27 19:52 ` Rutger Helling
2017-12-27 23:20 ` Leo Famulari
2017-12-28 5:50 ` Rutger Helling [this message]
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=20171228065012.589e2724@mykolab.com \
--to=rhelling@mykolab.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.