Thanks for clearing that up.
So it appears that getting the support of upstream to work on packages
would be a great amount causing user base to be "stuck". I wasn't aware
that there was so many packages and our manpower is too low to impact
upstream. I believe debian went back to ffmpeg a year
11.9 is the latest patch release on the 11.x branch, 12.0 is also in
portage but not marked stable. Neither provides the same versions of the
component libraries as ffmpeg even as old as ffmpeg 3.0.x (bearing in mind
ffmpeg is already u pto 3.3 branch, 3.0.x is already quite old). There may
be
Wasn't libav 11.9 released last month?
On Mon, May 1, 2017 at 9:43 AM, Ben Roberts
wrote:
> Let's bear in mind the problem is not just that there are packages that
> don't have direct support for libav. The problem is also partly that there
> is not a libav release
Let's bear in mind the problem is not just that there are packages that
don't have direct support for libav. The problem is also partly that there
is not a libav release that provides all the same component library
versions that are available in ffmpeg; libav is definitively behind ffmpeg
at the
Can we get a list of every application in portage that DOES NOT support
libav and requires ffmpeg?
I would volunteer to attempt filing bugs for each application requesting
libav support.
On Mon, May 1, 2017 at 9:31 AM KJS wrote:
> I have to agree with Ettore
>
> On Mon, May
I have to agree with Ettore
On Mon, May 1, 2017 at 6:02 AM, SÅ‚awomir Nizio
wrote:
> > We are one of the few distributions (actually i'm not aware of others)
> > that support libav out of the box, and i'm proud of it. What i would
> > propose instead is trying to push
> We are one of the few distributions (actually i'm not aware of others)
> that support libav out of the box, and i'm proud of it. What i would
> propose instead is trying to push upstream projects that misses libav
> support and/or helping libav providing support to them.
Volunteers? :)
One of