emerging either ffmpeg or libav, whichever you prefer, would have done it, without messing around with package.mask. USE-flags must correlate between virtual and ffmpeg/libav.

Afaik packages depending on media-video/ffmpeg are not yet ready for the move to virtual/ffmpeg and libav, I had to manually move some ebuilds into a local overlay, editing DEPENDS to the virtual._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

Last edited by genstorm on Sun Mar 27, 2011 9:02 pm; edited 1 time in total

That's a key.
If you don't set the use flags that are in virtual/ffmpeg to the same values for your installed ffmpeg or libav then you will always see blockers as emerge will try to install the other package._________________A mouse is a device used to point at the xterm you want to type in.

in my case and system , only chromium depends on media-video/ffmpeg , it don't detect virtual/ffmpeg, at this time, and make conflict wiht media-video/libva and ffmpeg, then what it's better option to use?

You can wait for the chromium maintainer to make the dependency on virtual/ffmpeg instead of media-video/ffmpeg, or copy the ebuild to a local overlay (with a revision number bump) and modify that line in the dependencies yourself.

I’ve added media-video/libav ebuild, which is fork of good old ffmpeg. In order to let you users decide what you want to use there also is virtual package called virtual/ffmpeg (which is now being integrated into ebuilds and updated back to versioned virtuals [currently there is just one virtual/ffmpeg with no version specified]) so when everything is migrated to it you can decide yourself if you want the old ffmpeg or the new libav.

The media-video/mplayer2 was added by Luca (lu_zero), but I removed the internal ffmpeg linking since this thing can link to your system ffmpeg (yay!). This change can make quite few of you unhappy because the internal ffmpeg was already ffmpeg-mt (threads!!!!), but technicaly with external linking you can just alter your ffmpeg to be whatever you want it and use the threading features in all apps linking against it. Given that I already like and use mplayer2 and I was the guy who did most snapshot bumps in mplayer1 lately it might be good idea for you lads (at least those in testing) to move with me

this is the worst thing i've saw, an howto be like oracle while been opensource...
pretty lame and they should be ashame.
if i understood the story (always hard to really catch all, i'm sure even them aren't sure of everything), some of them were disagreeing the dictator guy was reviewing the code and mostly reject it because "not as good as he could do it", ending with others devs loosing faith.
And because they think they could own the name, they fork and try to grab ffmpeg name and structure (as they were admin the servers), all that just to remove the commiter/reviewer !
Pretty lame, could understand why they do it, coudln't get why they do it like that! Just to remove this guy, was he so dictator that noone could remove him ?
Could understand also why they wish grab the project name, because all users knew that name, while libav will start from 0 on popularity, but it's like they cheat us, without letting us choose. A bit insulting: don't let user choose, they're too dumb, let's just keep the name they will follow like sheeps.

Now if the dictator don't change his habit we should have
- ffmpeg = slow evolution+more speed/stability because of strict coding politic the guy use
- libav = fast evolution, less stability as they (still if i understood clear) wish more functions to be push even not well review/test (still the code will be stabilize and optimize, but later)

On paper, libav should gave better results if they don't put anarchy and build 2 branch unstable/stable

I should go with libav, i will just wait to see if they really could handle it, big project always need a main man (or men) to drive everyone to the right path. I just hope they get away with some guys that could do that instead of just coding.