all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
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 09:51:06 +0200	[thread overview]
Message-ID: <20151029095106.7fb8fb18@debian-netbook> (raw)
In-Reply-To: <20151028233651.112ce6cf@uwaterloo.ca>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

On Wed, 28 Oct 2015 23:36:51 -0400
Andy Patterson <ajpatter@uwaterloo.ca> wrote:

> Hey everyone,
> 
> Here's a simple patch which makes it easier to customize ffmpeg's
> configure flags when inheriting from the package.
> 
> 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?
> 
> Comments on this patch are welcomed, of course.

If we have problems with gnutls causing test failures on certain
architectures we could also just enable gnutls for the platforms that don't
have the issues.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-29  7:51 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 [this message]
2015-10-29 21:11 ` Ludovic Courtès

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=20151029095106.7fb8fb18@debian-netbook \
    --to=efraim@flashner.co.il \
    --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.