Bug 358919 (ffmpeg-virtual) – [tracker] Migration from media-video/ffmpeg to virtual/ffmpeg

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description tman 2011-03-14 18:25:28 UTC]

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

[Comment 1 Jeroen Roovers (RETIRED) 2011-03-16 03:48:58 UTC]

(In reply to comment #0)
> mor infor u will find under :

Please try to spell English correctly.

[Comment 2 Steve Dibb (RETIRED) 2011-03-16 16:37:02 UTC]

That's just the fork of ffmpeg.

[Comment 3 Oliver Freyermuth 2011-03-16 16:43:07 UTC]

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).

[Comment 4 tman 2011-03-16 16:52:35 UTC]

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

[Comment 5 Grégoire Favre 2011-03-16 22:48:53 UTC]

What to choose Libav or git://git.videolan.org/ffmpeg.git ?

[Comment 6 Steve Dibb (RETIRED) 2011-03-17 01:46:39 UTC]

(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.

[Comment 7 Tomáš Chvátal (RETIRED) 2011-04-05 14:03:18 UTC]

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.

[Comment 8 Samuli Suominen (RETIRED) 2011-04-22 07:36:28 UTC]

*** Bug 364447 has been marked as a duplicate of this bug. ***

[Comment 9 Tomáš Chvátal (RETIRED) 2012-05-16 12:47:57 UTC]

Since all tracker bugs are done if anything new pops up we will fix it per-case basis. Closing the tracker as fixed.