From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id B367A4770A
	for <ffmpegdev@gitmailbox.com>; Wed, 20 Sep 2023 12:47:29 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 87A2168C8A5;
	Wed, 20 Sep 2023 15:47:25 +0300 (EEST)
Received: from haasn.dev (haasn.dev [78.46.187.166])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 86D3A68C075
 for <ffmpeg-devel@ffmpeg.org>; Wed, 20 Sep 2023 15:47:19 +0300 (EEST)
Received: from haasn.dev (unknown [10.30.0.2])
 by haasn.dev (Postfix) with ESMTP id 3893F404F4
 for <ffmpeg-devel@ffmpeg.org>; Wed, 20 Sep 2023 14:47:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=haasn.xyz; s=mail;
 t=1695214039; bh=lM7ZKtwtiRkD7E96PLHxkHaugHbR7Q7dpIYlUIbB0+s=;
 h=Date:From:To:Subject:In-Reply-To:References:From;
 b=g29MZJGOccbmI1huhlUyciUpcWCQe33I3xwNCpFX443xpDYD8sHBv3YdbCQq5VtMJ
 IJ149CUjuVT2Ph5/2scpw1gUfgXzZ+9pjnZKJHNcsdebtSx4YfVNI5yhVxIGwerKCC
 bdzsd2wfyW2d5EilpVzM34Tzka3/ai2FKJCWx2Oo=
Date: Wed, 20 Sep 2023 14:47:19 +0200
Message-ID: <20230920144719.GB115703@haasn.xyz>
From: Niklas Haas <ffmpeg@haasn.xyz>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
In-Reply-To: <20230919191608.GE8640@pb2>
References: <20230410221428.GJ1164690@pb2> <20230919191803.GB35669@haasn.xyz>
 <20230919191608.GE8640@pb2>
MIME-Version: 1.0
Content-Disposition: inline
Subject: Re: [FFmpeg-devel] FFmpeg release 6.1
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/20230920144719.GB115703@haasn.xyz/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On Tue, 19 Sep 2023 21:16:08 +0200 Michael Niedermayer <michael@niedermayer.cc> wrote:
> what about merging libplacebo into FFmpeg for example ?
> As far as iam concerned you can have absolute final power about anything
> in that libplacebo inside FFmpeg.

To respond quickly to this point,

I'm not sure what merging libplacebo would improve to the status quo. As
far as I can tell, it would only make my life harder, at least if you
expect me to start caring about patches sent to the mailing list (as
opposed to using PR/MRs as I do currently).

I'm not sure what the goal would be, either, except dragging more code
into FFmpeg. Code that can easily live outside it, because the degree of
interoperation between the two is minimal. All relevant distros already
package both libplacebo and FFmpeg, so the "ease of distribution" ship
has sailed.

It would also make libplacebo releases now tied to FFmpeg releases,
which is an obvious downgrade for my own reverse dependents and a
significant downgrade to my current release process. The FFmpeg ABI
policy also seems wholly incompatible with the libplacebo ABI policy.

_______________________________________________
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".