| 1 |
On Sat, 2011-04-02 at 16:41 -0300, Alexis Ballier wrote: |
| 2 |
> On Saturday, April 02, 2011 07:02:54 AM Paweł Hajdan, Jr. wrote: |
| 3 |
> > On 3/31/11 9:37 AM, Tomáš Chvátal wrote: |
| 4 |
> > > Ok two versioned virtuals (0.5 0.6) are now in the tree if people need |
| 5 |
> > > to specify the version. |
| 6 |
> > |
| 7 |
> > Thank you, but it's still not enough for chromium. The virtual uses |
| 8 |
> > |
| 9 |
> > >=ffmpeg-0.6, and chromium is known to be broken with <ffmpeg-0.6_p25767. |
| 10 |
> > |
| 11 |
> > We need to require >=ffmpeg-0.6_p25767, not just 0.6. |
| 12 |
> > |
| 13 |
> > By the way, I still didn't have time to test with libav, but it seems |
| 14 |
> > that it's expected to be compatible. |
| 15 |
> |
| 16 |
> |
| 17 |
> iirc, this dep in chromium is due to the need for libavcore, but this lib has |
| 18 |
> been merged back to libavutil in latest snapshots (and thus chromium fails to |
| 19 |
> build); if chromium goes back to look for the functions in libavutil, you may |
| 20 |
> have chances to be compatible with 0.6 |
| 21 |
> |
| 22 |
> A. |
| 23 |
> |
| 24 |
|
| 25 |
I've reported that upstream 2 days ago and it was fixed yesterday. I'm |
| 26 |
running chromium-11.0.696.28 against libav-0.7_pre20110327 here and it |
| 27 |
works fine. |
Archives