ffmpeg change the project name and will continue under the name libav, i will set this report as a start request for this new package. mor infor u will find under : http://www.libav.org/index.html Reproducible: Always
(In reply to comment #0) > mor infor u will find under : Please try to spell English correctly.
That's just the fork of ffmpeg.
http://git.ffmpeg.org now also redirects to http://git.libav.org, which at least broke the ffmpeg-9999 ebuild which looks for ffmpeg.git, which is now called libav.git at the new location. Any ebuilds trying to checkout libswscale from the ffmpeg-git are broken by that, too (to me, only multimedia-overlay ffmpeg comes to mind affected by this).
it not just only a fork: read on the homepage : "March 13, 2011 We, as a group of FFmpeg developers, have decided to continue developing FFmpeg under the name Libav. All existing infrastructure will be transferred to the libav.org domain. " so we need it in near future this in any cases
What to choose Libav or git://git.videolan.org/ffmpeg.git ?
(In reply to comment #4) > it not just only a fork: read on the homepage : > > "March 13, 2011 > > We, as a group of FFmpeg developers, have decided to continue developing FFmpeg > under the name Libav. All existing infrastructure will be transferred to the > libav.org domain. > " > > so we need it in near future this in any cases Um, no, that means that there are two groups of developers, each with their own releases that are pretty much both ffmpeg. Picking one over the other means that we want to follow that upstream's path. The reasonable thing to do would be to provide both versions, if reasonable, and/or requested.
All usages should be now filled as separate bugs into this tracker. So now it is up to the maintainers or the time i have free cpu again so i can test things.
*** Bug 364447 has been marked as a duplicate of this bug. ***
Since all tracker bugs are done if anything new pops up we will fix it per-case basis. Closing the tracker as fixed.
