Hi

On Wed, Feb 26, 2025 at 04:35:52PM +0000, Soft Works wrote:
[...]
> 
> > What we could do is make it easier to build from source with extra
> > components:
> 
> [..]
> 
> 
> > - Build scripts that detect available libraries. Possibly build scripts
> >   that install devel packages for these libraries. Possibly even a build
> >   script that installs a Debian in a VM/container.
> > 
> > - Tweak the build system to let add a component by just dropping it in a
> >   subdirectory.
> 
> Yes, that's exactly what I mean. Currently, when adding custom filters
> (or codecs, muxers etc.), you need to make changes at various places
> and each time when rebasing or merging things around and managing
> versions, these things are causing conflicts.
> Or when you want to provide a filter/component to the community 
> (as source code), you can't provide a patch that could be applied to
> arbitrary ffmpeg versions.
> 
> Having a "plugins" directory that is automatically scanned for plugin
> code, or a command line parameter like
> 
> ./configure --plugindir=../myplugins
> 
> would be fine IMO.
> 
> And obviously much more agreeable for everybody than runtime
> plugins, even though I would favor having both 😊

ffmpeg-source-plugins/

And i would suggest to instead of the source, also to allow
files in that directory listing where to find the source

source-plugin speech2subtile
url https://github.com/someone/somerepo/tree/$PLUGIN_VERSION or https://someplace/speech2subtile.$PLUGIN_VERSION.tar.gz(.sig)
gpg-key-fingerprint 24CE01CE9ACC5CEB74D88D9DB063D99736E54C93

that then could download a release tarball, and signature
get the gpg key from the key fingerprint
check the tarball to be authentic
and extract

This is simple (like 5 lines of code) and allows plugin authors to
update their plugins without everyoen having to re-download.


thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle