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 A470D1384DD for ; Wed, 16 Jan 2013 12:59:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CA8AC21C043; Wed, 16 Jan 2013 12:59:26 +0000 (UTC) Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D4F0321C030 for ; Wed, 16 Jan 2013 12:59:25 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id c11so2363688ieb.33 for ; Wed, 16 Jan 2013 04:59:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=nCTF/45Vzq6nSGhDuwaynBUkhi2Mr9H02lfcAnwSRnY=; b=u7Zj61Y/whNnBoIqHigoz1NIVkqmsU8z6+JiLnPuZWevgdNWFRU/OrYRmEV0r5KQFd 6RDoqKDFFJEeXdjPlrYbcs2FsaX9QD/+X1FYmaUCXvg1pyY9Z5pzw+FxabUNo8XEML1k SFYZvk0pGWER65VM4UroyK9HbzzlDePNPLbXTcYVJMNN/Wr8qrPoeU8O+zfpzLEojNPi AIzvZ8vZPsDDwvlWJ7DQ14WTo9/+SS1RVOOQQxqFBnUh6tKw18rIaaebD1/YSIBtzc1p ROPlnEdBT04ypAZtnOZiR5mFzYQDJFSyLKF1M2YcentyQMGewM3p7rYqW69emJqpFEAz bRwA== 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 X-Received: by 10.50.237.5 with SMTP id uy5mr730004igc.12.1358341165164; Wed, 16 Jan 2013 04:59:25 -0800 (PST) Sender: freemanrich@gmail.com Received: by 10.64.30.231 with HTTP; Wed, 16 Jan 2013 04:59:25 -0800 (PST) In-Reply-To: <20130116085428.7103a2a3@gentoo.org> References: <50F4DC62.1010500@gentoo.org> <20130115095506.6e033640@gentoo.org> <50F63634.50701@gentoo.org> <20130116085428.7103a2a3@gentoo.org> Date: Wed, 16 Jan 2013 07:59:25 -0500 X-Google-Sender-Auth: 8nUds6AjJERMC-YYnj4OpipHEhw Message-ID: Subject: Re: [gentoo-dev] Chromium system ffmpeg From: Rich Freeman To: gentoo-dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 4ac334e2-325f-4c84-b7e5-cbd313ed17eb X-Archives-Hash: d98a9e157eadb71e2ba4ec970f629e96 On Wed, Jan 16, 2013 at 6:54 AM, Alexis Ballier wrote= : > On Tue, 15 Jan 2013 21:10:12 -0800 > ""Pawe=C5=82 Hajdan, Jr."" wrote: >> >> What when chromium upstream uses code more recent than latest ffmpeg >> release and it doesn't compile against latest release? > > Blame them, it's stupid to break support for the latest release. > Usually, it's quite trivial to maintain compatibility and you should > probably lobby upstream to get this as a rule, it'd make life simpler > for everyone. Or just patch releases not to use too bleeding-edge code > (see mplayer for example). While I agree in principle, that is much easier said than done. I think upstream is more likely to consider the concept of a linux distro broken than their code. The unpacked chromium distfile is 1.1G, of which 694M is third party source-code. The chromium team has done an excellent job of disabling much of that, but the upstream attitude clearly is to cherry-pick their dependencies. This is pretty typical for Google projects from what I've seen - ChromeOS basically is a fork of Gentoo with many packages being fairly dated, and Android does just about everything its own way, typically releasing third-party code into production before any upstream packages have access to it. Of course, we should encourage upstream to improve its practices. I just wouldn't count on it, so I think we need to give the chromium team discretion on just how much patching they think they can handle. They're obviously pretty good at it already. Rich