[FFmpeg-devel] [RFC] libpostproc splitout

[Anton Khirnov]

Quoting Michael Niedermayer (2024-11-08 17:17:42)
> On Fri, Nov 08, 2024 at 11:44:03AM +0100, Tomas Härdin wrote:
> > tor 2024-11-07 klockan 00:11 +0100 skrev Michael Niedermayer:
> > > Hi all
> > > 
> > > Should libpostproc be split out into a seperate source repository ?
> > > 
> > > Several people did over the years want libpostproc removed, and such
> > > a task was part of the submitted and approved STF 2024 projects.
> > > But when i recently started posting related work, tomas questioned
> > > if spliting libpostproc into a seperate source repository actually is a good idea.
> > > 
> > > No invoice was submitted yet, so we could likely still change
> > > this to something else, if thats what people prefer.
> > > 
> > > To clarify this a bit (as its a bit convoluted)
> > > Option A.
> > >     1. split libpostproc out so it builds and links fine (already done) (send to SPI/STF/Invoice in future)
> > >     2. develop test system for libpostproc (2024 future) (send to SPI/STF/Invoice in future)
> > >     3. actually remove libpostproc from master repository (2025 future) (send to SPI/STF/Invoice in future)
> > > Option B.
> > >     0. double check with STF/SPI that such change is ok
> > >     1. split libpostproc out so it builds and links fine (already done) (send to SPI/STF/ never send invoice)
> > >     2. develop test system for libpostproc (2024 future) (send to SPI/STF, never send invoice) (this will get used with the libpostproc inside FFmpeg)
> > >     3. renegotiate actual libpostproc task to something else the community wants
> > >     4. whoever does the new task sends invoices and gets the whole money for all 3 parts
> > > 
> > > This looks a bit convoluted as iam trying to minimize the annoyance for STF so
> > > we dont have issues in the future. (Iam especially avoiding moving any STF payments
> > > accross teh year end which is a issue IIUC for STF)
> > > 
> > > each of the 3 milestones is 5040 Euro
> > > 
> > > Please comment what you prefer, the
> > > A. split libpostproc out or
> > > B. leave libpostproc in ffmpeg and fund some other maintaince work with the 15k Euro
> > 
> > 15k sounds like money better spent on something else, for example
> > improving the build system. Circular dependencies are kind of ugly, but
> > they're not showstoppers given good build systems
> 
> my wish would be that the 15k could be spend on a plugin interface
> for libavfilter.
> 
> Something that on startup would scan ~/.ffmpeg/plugins/ or something like that
> and load all compatible ones.
> A restriction to a simple 1 input link, 1 output link with possibility of
> future extension would already cover likely 90% of use cases.
> 
> anton, would you be interrested to implement something like that for 15k ?

I am working in that direction anyway as a part of my other work, but
* doing it properly requires a ton of preparatory work (for which 15k is
  way too little)
* I am not a fan of doing things improperly

-- 
Anton Khirnov