From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Request for --disable-deprecated configure option
Date: Fri, 4 Apr 2025 20:53:30 +0200
Message-ID: <20250404185330.GS4991@pb2> (raw)
In-Reply-To: <CABPLAST8WawWJFMNubxBKu37sLowY5gFOsDOGb_fmH_6X9ktbg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]
Hi
On Thu, Apr 03, 2025 at 11:02:01AM +0200, Kacper Michajlow wrote:
> Hello,
>
> It would be nice to have configure time ability to disable all
> `FF_API_*` for testing purposes.
>
> As we know not all code can be marked to emit Wdeprecated.
> Specifically #defines doesn't emit any warning and it's easy to miss
> such depreciation before it's actually removed.
>
> The breakage of course is not big, but the main issue is that the
> current release version of a ffmpeg user won't be compatible with
> ffmpeg after API bump, without any period for transition.
>
> --disable-deprecated could be used for testing and ensuring that
> (next) API bump goes smoothly. For both ffmpeg and its users.
I think such a option (in some form) would be a good idea
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No great genius has ever existed without some touch of madness. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-04-04 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 9:02 Kacper Michajlow
2025-04-03 9:39 ` Martin Storsjö
2025-04-03 13:14 ` Kacper Michajlow
2025-04-04 18:53 ` Michael Niedermayer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250404185330.GS4991@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git