From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3E0CA1384A1 for ; Tue, 15 Jan 2013 04:35:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E5FAC21C075; Tue, 15 Jan 2013 04:34:58 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F007B21C03A for ; Tue, 15 Jan 2013 04:34:57 +0000 (UTC) Received: from pc-00124.menlough.dyndns.org (adsl-75-36-173-8.dsl.pltn13.sbcglobal.net [75.36.173.8]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id 02F5E33DA90 for ; Tue, 15 Jan 2013 04:34:56 +0000 (UTC) Message-ID: <50F4DC62.1010500@gentoo.org> Date: Mon, 14 Jan 2013 20:34:42 -0800 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] Chromium system ffmpeg X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB6DC056450C941C928C607E0" X-Archives-Salt: b40b5c51-3410-4f15-98d7-1e5703a7b4a3 X-Archives-Hash: 65244edb35c85e6e980d7aa72879e35e This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB6DC056450C941C928C607E0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'm trying to make Chromium be more compatible with more versions of ffmpeg: (although not stated there, that includes libav). Now the initial response there is not enthusiastic (which doesn't surprise me), but do you think there are some points useful for the discussion I'm not aware of? What are the main challenges of keeping up-to-date with latest ffmpeg API changes? How do other projects deal with that? If there is anything else you want to share/say about this, please do. Pawe=C5=82 --------------enigB6DC056450C941C928C607E0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) iEYEARECAAYFAlD03GsACgkQuUQtlDBCeQJKkQCfRQhrAO+veAD2C8yfuaZgcEUs 2FYAnjiO6gApMaHZGT60fef85bTcGl31 =36ZE -----END PGP SIGNATURE----- --------------enigB6DC056450C941C928C607E0--