From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-162072-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 6EE5A138A1A
	for <garchives@archives.gentoo.org>; Thu, 12 Feb 2015 00:18:41 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id A220DE08E1;
	Thu, 12 Feb 2015 00:18:35 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 8BBDDE08AF
	for <gentoo-user@lists.gentoo.org>; Thu, 12 Feb 2015 00:18:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by smtp.gentoo.org (Postfix) with ESMTP id 763233406FA
	for <gentoo-user@lists.gentoo.org>; Thu, 12 Feb 2015 00:18:33 +0000 (UTC)
X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level:
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5.5
	tests=[AWL=-0.491, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7,
	SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]
	autolearn=no
Received: from smtp.gentoo.org ([127.0.0.1])
	by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8lIqSi2BaZj0 for <gentoo-user@lists.gentoo.org>;
	Thu, 12 Feb 2015 00:18:27 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTPS id B8A17340750
	for <gentoo-user@gentoo.org>; Thu, 12 Feb 2015 00:18:26 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <lnx-gentoo-user@m.gmane.org>)
	id 1YLhU6-0004F6-EZ
	for gentoo-user@gentoo.org; Thu, 12 Feb 2015 01:18:22 +0100
Received: from wsip-174-76-82-7.no.no.cox.net ([174.76.82.7])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <gentoo-user@gentoo.org>; Thu, 12 Feb 2015 01:18:22 +0100
Received: from boxcars by wsip-174-76-82-7.no.no.cox.net with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <gentoo-user@gentoo.org>; Thu, 12 Feb 2015 01:18:22 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-user@lists.gentoo.org
From: =?UTF-8?B?wrtRwqs=?= <boxcars@gmx.net>
Subject: [gentoo-user] Re: USE="-libav ffmpeg"
Date: Wed, 11 Feb 2015 18:18:16 -0600
Organization: none
Message-ID: <20150211181816.59767565@sepulchrave.remarqs>
References: <loom.20150210T150925-174@post.gmane.org>
	<54DA165E.3060400@alectenharmsel.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: wsip-174-76-82-7.no.no.cox.net
X-Newsreader: Claws Mail 3.9.0 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
X-Archives-Salt: f1cb571a-900f-4473-9d07-d73d0222d908
X-Archives-Hash: e3a1b93ed64c39eb1a7b976e165bbb5e

On Tue, 10 Feb 2015 09:31:58 -0500
Alec Ten Harmsel <alec@alectenharmsel.com> wrote:

> On 02/10/2015 09:13 AM, James wrote:
> > Is this the best way to stay on ffmpeg?   (USE="-libav ffmpeg") ?  
> 
> Yes, as far as I know. 

Me too.

> There was a news item not too long ago about
> this; eselect news list gives a "2015-02-01  ffmpeg/libav conflict
> management: USE=libav" that you can read unless you've deleted it
> already. TL;DR is that 'ffmpeg' enables ffmpeg/libav support, 'libav'
> adds libav dependency, '-libav' adds ffmpeg dependency.

That news item was withdrawn and the changes reverted because they
wanted to consider handling it with a use_expand variable.  If they do
that, I guess we'll get another news item.  (And if they don't do that,
maybe we'll get the old news item back.)