| 1 |
On Wed, 2022-01-12 at 20:25 -0500, Matt Turner wrote: |
| 2 |
> On Tue, Jan 11, 2022 at 9:45 PM Georgy Yakovlev |
| 3 |
> <gyakovlev@g.o> wrote: |
| 4 |
> > |
| 5 |
> > it's an ancient codec that is barely used nowadays |
| 6 |
> > so let's disable it by default. |
| 7 |
> > Users are free to re-enable if required. |
| 8 |
> > |
| 9 |
> > Bug: https://bugs.gentoo.org/831044 |
| 10 |
> |
| 11 |
> Heh, looks like you want to leave it disabled by default because it |
| 12 |
> fails to compile on arm? :) |
| 13 |
> |
| 14 |
> I don't have a preference. I would note that a few packages depend on |
| 15 |
> it being enabled in ffmpeg: |
| 16 |
> |
| 17 |
> media-gfx/blender |
| 18 |
> media-libs/libopenshot |
| 19 |
> media-plugins/mythplugins |
| 20 |
Thanks for actually checking it =) |
| 21 |
|
| 22 |
I'm not on a crusade to disable it, just thought it's a sensible thing |
| 23 |
to do in 2022. |
| 24 |
|
| 25 |
I've opened a bug and asked maintainers for those packages to double- |
| 26 |
check if possible. |
| 27 |
|
| 28 |
My initial investigation (very brief) showed that it might be a catch- |
| 29 |
all dep or simply a historical dep that never got re-verified. |
| 30 |
|
| 31 |
https://bugs.gentoo.org/831211 |
Archives