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 4AC4B138CCF for ; Fri, 15 May 2015 18:52:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4920EE0841; Fri, 15 May 2015 18:52:12 +0000 (UTC) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 14D13E0802 for ; Fri, 15 May 2015 18:52:11 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so262612wic.0 for ; Fri, 15 May 2015 11:52:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=R2Dh1Qdv0V1NiR2toV6H+hmhUZxij77RuVcbEDrAyVs=; b=KzO7u+5rli2JnTF+OGksJVQIdKqron9mxZeuCVJ1/9UG6W8yGIYGusJSa+UTNr7BYM NrOtZVkFcWPNzXAN1S60+Z53FCcZxHNCcenZzs3GU2kTlxlVNihOwXKB0iU5xpvW+Ouz NJk/NayhWhQmcdyQdVnIikJSxYv8GZGRY2BbWo9xnpc/Bq3iPm8jPw/rPHBoQLM3xLZu dmGYQkVVd9gmdZhhAknjCCjDXqYHXKyJPSzRiTYSUdLPIrwT3Il8SPvbDcQ3dYUY9AB/ twGrIeYdfhxw76PwaDOOq+bX+b7f34tm2Xmsp6yTyP3PJb9PPWL4rPE3UzI+U/hJeanp qG3A== X-Received: by 10.180.19.100 with SMTP id d4mr36395363wie.29.1431715929935; Fri, 15 May 2015 11:52:09 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id gs7sm4539307wib.10.2015.05.15.11.52.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 May 2015 11:52:09 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] libav and ffmpeg on the same computer issue once again Date: Fri, 15 May 2015 19:51:52 +0100 User-Agent: KMail/1.13.7 (Linux/3.18.11-gentoo; KDE/4.14.3; x86_64; ; ) References: <55558dda.42dfc20a.6ffb.3e3d@mx.google.com> In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3171254.nBFGCCfIEP"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201505151952.01785.michaelkintzios@gmail.com> X-Archives-Salt: 46674c34-cb39-4a8b-8a01-8e0585044292 X-Archives-Hash: b59d203cd5f8126c1776d41a4a7d5b80 --nextPart3171254.nBFGCCfIEP Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Friday 15 May 2015 18:30:29 Alexander Kapshuk wrote: > On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: > > On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury > >=20 > > wrote: > > > I had a similar problem with some packages wanting virtual/ffmpeg and > > > it wouldn't take the -libav USE flag without adding a keyword for > > > ~amd64 on the virtual. > > > (yes, I am going the opposite way from you, but the cause seem the > > > same -- various USE flags are not yet adjusted in the stable > > > branches.) > > >=20 > > > Perhaps we need to request "stabilization" for some of the newer > > > packages to solve this. > >=20 > > Thank you for confirming that libav USE flag do not work not only for m= e. > >=20 > > However, it would be interesting to hear what the Gentoo devs think abo= ut > > this issue. >=20 > Portage news item No 19 has the answer you're looking for. >=20 > > eselect news read 19 > > 2015-04-16-ffmpeg-default > >=20 > > Title FFmpeg default > > Author Ben de Groot > > Posted 2015-04-16 > > Revision 1 > >=20 > > Since the choice between ffmpeg and libav has been made more > > explicit, there has been a lot of discussion about what the > > default implementation should be. It can be concluded that > > media-video/ffmpeg has wider support, and would be somewhat > > more convenient for most end-users. > >=20 > > For this reason the default implementation has been switched > > back from media-video/libav to media-video/ffmpeg by removing > > the libav useflag from the base profile. > >=20 > > If the libav useflag is already globally enabled or disabled > > in /etc/portage/make.conf, then no further action is required. > >=20 > > Users who implicitly relied on libav being enabled in their > > profile, and who wish to continue using libav, should enable > > USE=3Dlibav in their /etc/portage/make.conf file. No, this is not yet 100% true, or at least not true for some packages, whic= h=20 are also pulling in abi_x86_32 versions. I came across this problem something like a week ago on a PC with no ffmpeg= or=20 libav USE flags. I tried setting USE=3D"-libav" and also +ffmpeg, but coul= dn't=20 fix the blockers. Eventually, I uninstalled the hard blockers like 'media- libs/libpostproc' and then rebuilt any packages already installed which wer= e=20 causing portage to complain/want libav. Can't recall fully which packages= =20 these were, k3b springs to mind. There may be a more scientific way of resolving the conflict, but that's ho= w I=20 got around this problem. HTH. =2D-=20 Regards, Mick --nextPart3171254.nBFGCCfIEP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJVVkBRAAoJELAdA+zwE4Yel+wH/RIRhQsXLNQy5kJ+yhw3+hTG 1UNzjBfYW4PQ8h8ok0IwZpisS/USU+cHCTfj/okTBrf+fPRB271t9gWrAcHEzL1Q HmrAJgDgA4zPp9On3fsstrB7IjSoK/UFrBiFtsR9dR8ZAIbj9WSyYh1C3ETPdaGL pSQ1ZpORYmHkE8xcscltYzHdZ9cmViK2OZPe4vL02qqNYD8twsTrSXvApyC1swVh vz8KVPIvu1TlKt9VcTL3k5vQNpfAljbIXO31f6YiraLBvMeSsHVqhr7w4F+F2B6J OM9ozLrvuK1913LMi+E5JL9sES15qHN4ruliDEUbN1SH1jiXkItAAJhlDxkZsI8= =nps3 -----END PGP SIGNATURE----- --nextPart3171254.nBFGCCfIEP--