bug#61792: closed ([PATCH] gnu: ffmpeg: enable libwebp)

[GNU bug Tracking System]

Your message dated Wed, 1 Mar 2023 23:02:51 -0500
with message-id <ZAAf602t0xq52OJO@jasmine.lan>
and subject line Re: [bug#61792] [PATCH] gnu: ffmpeg: enable libwebp
has caused the debbugs.gnu.org bug report #61792,
regarding [PATCH] gnu: ffmpeg: enable libwebp
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
61792: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61792
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [PATCH] gnu: ffmpeg: enable libwebp
>
>
>
>
> Date: 
>
> Sat, 25 Feb 2023 11:56:46 -0800
>
>
>
>
> * gnu/packages/video.scm (ffmpeg)[configure-flags]: --enable-libwebp
>
> Signed-off-by: Ryan Sundberg <ryan@arctype.co>
> ---
>  gnu/packages/video.scm | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/gnu/packages/video.scm b/gnu/packages/video.scm
> index f63d5494de..f64608d18a 100644
> --- a/gnu/packages/video.scm
> +++ b/gnu/packages/video.scm
> @@ -1634,6 +1634,7 @@ (define-public ffmpeg-5
>              libvdpau
>              libvorbis
>              libvpx
> +            libwebp
>              libx11
>              libx264
>              mesa
> @@ -1731,6 +1732,7 @@ (define-public ffmpeg-5
>           "--enable-libvidstab"
>           "--enable-libvorbis"
>           "--enable-libvpx"
> +         "--enable-libwebp"
>           "--enable-libxvid"
>           "--enable-libx264"
>           "--enable-libx265"
> -- 
> 2.37.2
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: [bug#61792] [PATCH] gnu: ffmpeg: enable libwebp
>
>
>
>
> Date: 
>
> Wed, 1 Mar 2023 23:02:51 -0500
>
>
>
>
> On Wed, Mar 01, 2023 at 12:13:37AM -0800, Ryan Sundberg wrote:
> > Surprisingly, this flag is supported all the way back to ffmpeg-3. So I
> > tested guix shell ffmpeg@5 ffmpeg@4 ffmpeg@3 and ffmpeg@2 (which clears
> > all configure flags), all builds passed.
>
> Great! I removed the input from ffmpeg-2.8, since it wouldn't have been
> used anyways (although it is supported), and pushed as
> 03b463b68ba62b0b6f11a585240829fddef37f48
>
>
> --- End Message ---