Re: [gentoo-user] libav and ffmpeg on the same computer issue once again

[Alexander Kapshuk]

On Fri, May 15, 2015 at 9:04 AM, Gevisz <gevisz@×××××.com> wrote:

> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury <redwolfe@×××××.com>
> 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.)
> >
> > Perhaps we need to request "stabilization" for some of the newer
> > packages to solve this.
>
> Thank you for confirming that libav USE flag do not work not only for me.
>
> However, it would be interesting to hear what the Gentoo devs think about
> this issue.
>


Portage news item No 19 has the answer you're looking for.


> eselect news read 19
> 2015-04-16-ffmpeg-default
>   Title                     FFmpeg default
>   Author                    Ben de Groot <yngwin@g.o>
>   Posted                    2015-04-16
>   Revision                  1
>
> 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.
>
> 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.
>
> If the libav useflag is already globally enabled or disabled
> in /etc/portage/make.conf, then no further action is required.
>
> Users who implicitly relied on libav being enabled in their
> profile, and who wish to continue using libav, should enable
> USE=libav in their /etc/portage/make.conf file.
>