all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Patterson <ajpatter@uwaterloo.ca>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: ffmpeg: Move flags into their own argument.
Date: Thu, 29 Oct 2015 22:11:48 +0100	[thread overview]
Message-ID: <87io5p752j.fsf@gnu.org> (raw)
In-Reply-To: <20151028233651.112ce6cf@uwaterloo.ca> (Andy Patterson's message of "Wed, 28 Oct 2015 23:36:51 -0400")

Andy Patterson <ajpatter@uwaterloo.ca> skribis:

> The reason I wanted to do this was so that I could enable TLS support
> for ffmpeg locally. The comment in the configure flags specifies that
> the tests fail with gnutls support enabled. The tests are currently
> working for me with gnutls enabled, on AMD64. I'd like to send another
> patch to enable it. Does anyone have any concerns about doing so?

It turns out that FFmpeg already depends on GnuTLS via libquvi, per:

  guix graph -t references ffmpeg | dot -Tps > t.ps

So I would say that you can add it in a separate patch without any
problems.

> From c78491cc816d936722ec403e8bd498162abcf962 Mon Sep 17 00:00:00 2001
> From: Andy Patterson <ajpatter@uwaterloo.ca>
> Date: Wed, 28 Oct 2015 22:42:42 -0400
> Subject: [PATCH] gnu: ffmpeg: Move flags into their own argument.
>
> * gnu/packages/video.scm (ffmpeg)[arguments]: Move the configurable
>   configure flag literals into the configure-flags argument. Call
>   configure with these flags from the configure phase.

Applied, thanks!

Ludo’.

      parent reply	other threads:[~2015-10-29 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  3:36 [PATCH] gnu: ffmpeg: Move flags into their own argument Andy Patterson
2015-10-29  7:51 ` Efraim Flashner
2015-10-29 21:11 ` Ludovic Courtès [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=87io5p752j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=ajpatter@uwaterloo.ca \
    --cc=guix-devel@gnu.org \
    /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.