From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 90B7B4532B for ; Sat, 21 Jan 2023 22:01:10 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C6B8F68BB11; Sun, 22 Jan 2023 00:01:07 +0200 (EET) Received: from iq.passwd.hu (iq.passwd.hu [217.27.212.140]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 103C86802C8 for ; Sun, 22 Jan 2023 00:01:01 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by iq.passwd.hu (Postfix) with ESMTP id 1B570E7324 for ; Sat, 21 Jan 2023 23:00:58 +0100 (CET) X-Virus-Scanned: amavisd-new at passwd.hu Received: from iq.passwd.hu ([127.0.0.1]) by localhost (iq.passwd.hu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuUeDmLYCUQv for ; Sat, 21 Jan 2023 23:00:53 +0100 (CET) Received: from iq (iq [217.27.212.140]) by iq.passwd.hu (Postfix) with ESMTPS id EFD0BE6301 for ; Sat, 21 Jan 2023 23:00:52 +0100 (CET) Date: Sat, 21 Jan 2023 23:00:52 +0100 (CET) From: Marton Balint To: FFmpeg development discussions and patches In-Reply-To: <20230121213629.GZ1949656@pb2> Message-ID: <8b99815-8f2f-8366-68c3-82fe7698c36b@passwd.hu> References: <20230116133840.512-1-jamrial@gmail.com> <167407008302.4503.12911207010634660934@lain.khirnov.net> <20230120020509.GX1949656@pb2> <167431989409.26119.3043585718968218@lain.khirnov.net> <20230121213629.GZ1949656@pb2> MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 00/26] Major library version bump X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Sat, 21 Jan 2023, Michael Niedermayer wrote: > On Sat, Jan 21, 2023 at 05:51:34PM +0100, Anton Khirnov wrote: >> Quoting Michael Niedermayer (2023-01-20 03:05:09) >>> PS: iam not sure i fully understood the reason behind why versions should be >>> set to "wrong" values during some period, so as always i might be missing >>> something >> >> The reason is that after the major bump, the API and ABI are declared to >> be unstable for some period, so people can freely >> - break ABI, e.g. by reordering struct members >> - modify API added during the instability period in an arbitrary way >> without a new major bump for every such change, that would be normally >> required. >> >> My concern is that the instability period is quite long and there is >> very little indication for our users that they cannot depend on the >> ABI/API being stable. So I'm proposing to introduce some mechanism to >> make this more visible for our callers. >> >> Alternatively, we could just not have an instability period at all. > > Does anyone plan to use the next bumps instability period for anything ? > If so, i assume theres a good reason why it cannot be done without such > period easily? AVCodecContext->frame_number should be changed to int64_t. I guess you could do something similar which was done for buffer_size_t, but that seems like a lot of extra work and ifdefry for questionable benefit. Regards, Marton > > If theres noone -> easy solution, we need no instability period ATM. > If theres someone, i would ask that someone how long it needs to be > and write that down in APIchanges. Maybe as in "API is unstable becuase > of X until 2033-11-11 > > a new #define LIBAVCODEC_UNSTABLE could be added but izt feels a bit > overengeneered. This whole thing is more a exception, isnt it? > > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > While the State exists there can be no freedom; when there is freedom there > will be no State. -- Vladimir Lenin > _______________________________________________ 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".